Device and method for providing external access to multi-drop bus peripheral devices

ABSTRACT

An electronic device includes a slave interface configured for coupling to a machine controller of a machine via a multi-drop bus (MDB), a host interface configured for coupling to a first peripheral device of the machine, and memory storing one or more programs to be executed by the one or more processors and comprising instructions for: registering the electronic device as a slave to the machine controller, registering the first peripheral device as a slave to the electronic device, receiving from a mobile device a request to access signals generated by the first peripheral device, validating the request, and sending a reset command to the first peripheral device via the host interface, the reset command including a directive to update a signal destination address of the first peripheral device from a controller address of the machine controller to a device address of the electronic device.

PRIORITY CLAIM

The present application is a continuation of U.S. patent applicationSer. No. 16/934,933, filed Jul. 21, 2020, which is hereby incorporatedby reference in its entirety.

U.S. patent application Ser. No. 16/934,933 is a continuation-in-part ofU.S. patent application Ser. No. 15/406,492, filed Jan. 13, 2017 andissued as U.S. Pat. No. 10,719,833 on Jul. 21, 2020, which is acontinuation of U.S. patent application Ser. No. 14/335,762, filed Jul.18, 2014 and issued as U.S. Pat. No. 9,547,859 on Jan. 17, 2017, whichis a continuation of U.S. patent application Ser. No. 14/214,644, filedMar. 14 2014 and issued as U.S. Pat. No. 8,856,045 on Oct. 7, 2014,which claims priority to U.S. Provisional Patent Application No.61/917,936, filed Dec. 18, 2013, and is a continuation-in-part of U.S.Design patent application No. 29/477,025, filed Dec. 18, 2013 and issuedas U.S. Pat. No. D755,183 on May 3, 2016, each of which is herebyincorporated by reference in its entirety.

U.S. patent application Ser. No. 16/934,933 is also acontinuation-in-part of U.S. patent application Ser. No. 16/029,483,filed Jul. 6, 2018 and issued as U.S. Pat. No. 10,963,905 on Mar. 30,2021, which is a continuation of Ser. No. 14/611,065, filed Jan. 30,2015 and issued as U.S. Pat. No. 10,019,724 on Jul. 10, 2018, each ofwhich is hereby incorporated by reference in its entirety.

U.S. patent application Ser. No. 16/934,933 is also acontinuation-in-part of U.S. patent application Ser. No. 15/893,514,filed Feb. 9, 2018, which claims priority to International PatentApplication No. PCT/US17/15676, filed Jan. 30, 2017, which is acontinuation of U.S. Provisional Patent Application No. 62/289,158,filed Jan. 29, 2016. U.S. patent application Ser. No. 15/893,514 is alsoa continuation-in-part of U.S. patent application Ser. No. 14/641,236,filed Mar. 6, 2015, which claims priority to U.S. Provisional PatentApplication No. 62/081,492, filed Nov. 18, 2014. U.S. patent applicationSer. No. 14/641,236 is also a continuation-in-part of U.S. patentapplication Ser. No. 14/320,534, filed Jun. 30, 2014, which is acontinuation-in-part of U.S. patent application Ser. No. 14/214,644,filed Mar. 14 2014 and issued as U.S. Pat. No. 8,856,045 on Oct. 7,2014, which claims priority to U.S. Provisional Patent Application No.61/917,936, filed Dec. 18, 2013, and is a continuation-in-part of U.S.Design patent application No. 29/477,025, filed Dec. 18, 2013 and issuedas U.S. Pat. No. D755,183 on May 3, 2016, each of which is herebyincorporated by reference in its entirety.

TECHNICAL FIELD

The present application relates to the field of electronic peripheraldevices, and in particular, to a system for providing access to anelectronic peripheral device over a non-persistent network connection.

BACKGROUND

Master/slave technology uses a model of dualistic communication whereone device or process (the master) has control over one or more otherdevices (the slave(s)), sometimes referred to as peripheral devices.

Peripheral devices are often disposed at the functional interfacebetween various internal components of a machine and a user of thosecomponents, thereby enabling human/machine interaction. While some typesof peripheral devices may be removed and replaced (e.g., a UniversalSerial Bus (USB) mouse or keyboard) or accessed by outside devices(e.g., a wireless printer), other types of peripheral devices, such as abill acceptor or card reader, may be embedded in a machine and dependenton aspects of the machine (such as the machine's power supply,processing system, and physical housing) to operate.

As the number of people with Internet-connected mobile devicesproliferates, so does the variety of uses for such devices. Some usesmay be enhanced or even require certain types of peripheral deviceswhich have traditionally only been accessible in embedded systems whichdo not necessarily provide access to outside devices.

SUMMARY

Disclosed herein is a system for providing external access to electronicperipheral devices disposed in a machine. The system enables an externaldevice to access functionality provided by an electronic peripheraldevice of a machine by providing wireless communications between amobile application and the electronic peripheral device. In order toprovide this access, the system (i) communicatively decouples theelectronic peripheral device from a machine controller which normallywould function as the master of the electronic peripheral device, and(ii) communicatively couples the electronic peripheral device with themobile application which functions as the master of the electronicperipheral device until the mobile application no longer requires accessto the functionality provided by the electronic peripheral device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram that shows three zones: a “communicationzone” (e.g., Bluetooth range), an “authorization zone,” and a “paymentzone” in accordance with some implementations.

FIG. 2 is a schematic diagram that shows the three zones of FIG. 1 withmultiple users therein in accordance with some implementations.

FIG. 3 is a table that illustrates the hands-free credit or alert userprinciple in accordance with some implementations.

FIG. 4 is a flow chart showing the logging received signal strengthindicator (RSSI) information in accordance with some implementations.

FIG. 5 is a block schematic that shows elements of the paymentprocessing system including, but not limited to, the adapter module, themachine, the mobile device, and servers, as well as communicationstherebetween in accordance with some implementations.

FIG. 6 is a block schematic that shows three areas of encryption used(each is bi-directional) between the adapter module, the machine, themobile device, and/or servers in accordance with some implementations.

FIG. 7 is a block diagram that shows communications, messaging, vendingsequence, and purchase flow between the adapter module, the mobiledevice, and a system management server in accordance with someimplementations.

FIG. 8A is a schematic process flow diagram that shows additionalelements and features of the payment processing system (e.g.,communications, messaging, vending sequence, and purchase flow) when theuser enters the “communication zone” (e.g., Bluetooth range) inaccordance with some implementations.

FIG. 8B is a schematic process flow diagram that shows additionalelements and features of the payment processing system (e.g.,communications, messaging, vending sequence, and purchase flow) when theuser enters the “authorization zone” in accordance with someimplementations.

FIG. 8C is a schematic process flow diagram that shows additionalelements and features of the payment processing system (e.g.,communications, messaging, vending sequence, and purchase flow) when theuser enters the “payment zone” and, in particular, detailing ahands-free mode embodiment and a swipe mode embodiment in accordancewith some implementations.

FIG. 8D is a schematic process flow diagram that shows additionalelements and features of the payment processing system (e.g.,communications, messaging, vending sequence, and purchase flow) in avending transaction including a loop for multiple transactions inaccordance with some implementations.

FIG. 8E is a schematic process flow diagram that shows additionalelements and features of the payment processing system (e.g.,communications, messaging, vending sequence, and purchase flow) in thelogin mode in accordance with some implementations.

FIG. 8F is a schematic process flow diagram that shows additionalelements and features of the payment processing system (e.g.,communications, messaging, vending sequence, and purchase flow) duringboot-up of the adapter module in accordance with some implementations.

FIG. 8G is a schematic process flow diagram that shows additionalelements and features of the payment processing system (e.g.,communications, messaging, vending sequence, and purchase flow) duringan account check/update process in accordance with some implementations.

FIGS. 9A-9E are flow charts that show example steps and features of thepayment processing system (e.g., communications, messaging, vendingsequence, and purchase flow) in accordance with some implementations.

FIGS. 10A-10D show a mobile device with a graphical representation of amobile application shown thereon, the mobile application being used aspart of the mobile-device-to-machine payment processing system inaccordance with some implementations.

FIG. 11 is a perspective view of the in-line dongle adapter module inaccordance with some implementations.

FIG. 12 is a front plan view of the in-line dongle adapter module ofFIG. 11 in accordance with some implementations.

FIG. 13 is a back plan view of the in-line dongle adapter module of FIG.11 in accordance with some implementations.

FIG. 14 is a side view of the in-line dongle adapter module of FIG. 11in accordance with some implementations.

FIG. 15 is a first end view of a connector receptacle of the in-linedongle adapter module of FIG. 11 in accordance with someimplementations.

FIG. 16 is a second end view of a connector receptacle of the in-linedongle adapter module of FIG. 11 in accordance with someimplementations.

FIG. 17 is a perspective view taken from the first end of the in-linedongle adapter module of FIG. 11, the connectors and cables betweenwhich the in-line dongle adapter module is inserted being shown inbroken lines for illustrative purposes in accordance with someimplementations.

FIG. 18 is a perspective view taken from the second end of the in-linedongle adapter module of FIG. 11, the connectors and cables betweenwhich the in-line dongle adapter module is inserted being shown inbroken lines for illustrative purposes in accordance with someimplementations.

FIG. 19 is a perspective view of the in-line dongle adapter module ofFIG. 11 within a vending machine in accordance with someimplementations.

FIG. 20 is a block diagram of an adapter module in accordance with someimplementations.

FIG. 21 is a block diagram of a mobile device in accordance with someimplementations.

FIG. 22 is a block diagram of a server in accordance with someimplementations.

FIG. 23 is a schematic flow diagram of a process for authenticating auser to perform a transaction in the payment processing system inaccordance with some implementations.

FIG. 24A is a block diagram of a packet of information broadcast by thepayment module (sometimes also herein called the “adapter module”) inaccordance with some implementations.

FIG. 24B is a block diagram of an authorization request in accordancewith some implementations.

FIG. 24C is a block diagram of an authorization grant token inaccordance with some implementations.

FIG. 24D is a block diagram of transaction information generated by thepayment module in accordance with some implementations.

FIG. 25 is a schematic flow diagram of a process for processingacknowledgment information in the payment processing system inaccordance with some implementations.

FIG. 26 is a block diagram of a device for retrofitting a paymentaccepting unit (e.g., machine 120) to accommodate a plurality of paymentperipherals in accordance with some implementations.

FIG. 27 is a schematic flow diagram of a payment peripheral registrationprocess in accordance with some implementations.

FIGS. 28A-28B illustrate a schematic flow diagram of a payment processin accordance with some implementations.

FIG. 29 illustrates a flowchart diagram of a method of retrofitting apayment accepting unit to accommodate a plurality of payment peripheralsin accordance with some implementations.

FIG. 30A-30B illustrate a block diagram of normal and interceptoperations of a device for retrofitting a payment accepting unit (e.g.,machine 120) to provide external access to an electronic peripheraldevice in accordance with some implementations.

FIGS. 31-34 illustrate schematic flow diagrams of a process forproviding external access to an electronic peripheral device inaccordance with some implementations.

FIGS. 35A-35B show a mobile device with a graphical representation of amobile application shown thereon, the mobile application being used aspart of a peripheral access system in accordance with someimplementations.

Like reference numerals refer to corresponding parts throughout theseveral views of the drawings.

DETAILED DESCRIPTION

Disclosed herein is a payment processing system or, more specifically, amobile-device-to-machine payment processing system for processingtransactions over a non-persistent network connection. Themobile-device-to-machine payment processing system disclosed hereinfocuses on the unattended retail space (e.g., a payment accepting unit120, sometimes also herein called a “machine 120”). More specifically,the mobile-device-to-machine payment processing system disclosed hereinallows a user (having a mobile device 150 with a mobile application 140thereon) to make a cashless purchase from a payment accepting unit 120(having an adapter module 100 associated therewith).

The mobile-device-to-machine payment processing system described hereincan be implemented with one or more of the following features: easyinstallation feature, a non-persistent network connection feature; amanual (swipe to pay) mode feature; a hands-free mode feature; and amultiple vending transactions (multi-vend) feature.

Easy Installation: Installation is very easy, requires no tools,requires no configuration, and takes as little as 30 seconds. This isaccomplished by using an adapter module 100 (sometimes also hereincalled “payment module 100”) such as an in-line dongle (a hardwaredevice with software thereon) design for in-line insertion within amulti-drop bus (MDB) of a payment accepting unit 120 (e.g., a vendingmachine) (sometimes also herein called ‘the machine 120”). Installationis as simple as “powering down” (turning off) the machine 120,identifying the “wire” that connects with a payment receiving mechanism(e.g., the coin mechanism), disconnecting the wire (so that there aretwo loose ends, such as a male connection end or adapter of an MDB and afemale connection end or adapter of an MDB), plugging (inserting) theadapter module 100 in serial (“in-line”) with the wire (e.g., connectingthe MDB female adapter to a male adapter of the adapter module 100 andconnecting the MDB male adapter to a female adapter of the adaptermodule 100), tucking the wire and the installed adapter module 100 backinto position, and “powering up” (turning on) the machine 120. Mostvending machines made since 1995 have this industry standard MDBtechnology that would allow this easy 30-second installation. Onmachines without MDB technology, the adapter module 100 can beconfigured or designed to work with other serial protocols or activate aswitch. In essence the adapter module 100 simulates establishing paymenton payment accepting unit 120 in much the same manner as otheralternative forms of payment (e.g., cash).

Non-persistent Network Connection: Although payment accepting units (or“machines”) that accept only cash (e.g., paper currency and coins) maynot require a connection (persistent or non-persistent) to a network,traditional payment accepting units that accept cashless payments (e.g.,credit cards, debit cards, and alternative mobile device payment methodsusing, for example, smart phones) require a persistent connection to anetwork (wired or wireless) to facilitate the cashless payments. Inother words, without a persistent (ongoing or accessible on demand)network connection, traditional payment accepting units cannot acceptcashless payments. Most traditional payment accepting units that acceptcashless payments include the technology to accomplish this persistentnetwork connection that allows them to connect to a remote server. Ifthe network connection to a traditional machine is temporarilyinterrupted, cashless payments will be temporarily unavailable. If themachine is located in a location where no network connection isavailable, cashless payments is not possible. In addition to using amobile device 150 as an intermediary between the payment accepting units120 and the server 130, the mobile-device-to-machine payment processingsystem described herein minimizes (i.e., the manual mode) or eliminates(i.e., the hands-free mode) user interaction with the mobile device 150.Further, in some implementations, the mobile-device-to-machine paymentprocessing system described herein facilitates the acceptance ofcashless payments without requiring any network connection near thepayment accepting unit 120. In some implementations, when themobile-device-to-machine payment processing system described herein islocated in a remote location where network connection is unavailable,the mobile-device-to-machine payment processing system, therefore, canstill accept cashless payments.

Manual (Swipe-to-Pay) Mode: Using a “swipe-to-pay” feature (or just“swipe”) refers to a user's action implemented on his/her mobile device150 where he/she quickly brushes his/her finger (or other pre-determinedinteraction) on the mobile device's touch screen 152 (FIGS. 10A-10D) orother input devices associated with the mobile device 150. From theuser's perspective, when the user is within range, a pre-installedmobile application 140 automatically connects to the payment acceptingunit 120 (e.g., a vending machine). The mobile application 140 mightdisplay (on the touch screen 152) a prepaid balance that the user“swipes” to transfer payment to the payment accepting unit 120. The usercould observe the transferred funds on the touch screen 152 of themobile device 150 and/or on the display 122, 124 (FIG. 19) of thepayment accepting unit 120. The transaction is completed just as if cashwas inserted in the machine 120 with the user inputting his selection onthe payment accepting unit 120 and the payment accepting unit 120dispensing the product or service. After the selection is made, thechange is returned to the mobile device 150 and this may be shown on thetouch screen 152 of the mobile device 150.

Hands-Free Mode: A “hands-free pay” feature (or just “hands-free”) wouldmost likely be used with “favorite” payment accepting units 120 (e.g., afrequently used vending machine at a user's work or school). From theuser's perspective, he/she would approach the favorite payment acceptingunit 120 and notice that the display 122, 124 (FIG. 19) of the paymentaccepting unit 120 shows funds available, he/she would select theproduct or service using the payment accepting unit's input mechanisms(e.g., buttons 126 or a touch screen display 124 shown in FIG. 19), andhe/she would retrieve dispensed services or products. It would be thatsimple. More specifically, when the user is within range, apre-installed mobile application 140 automatically connects to thepayment accepting unit 120 (e.g., a vending machine). The user may leavethe mobile device 150 in a pocket, purse, briefcase, backpack, or othercarrier. As the user approaches the payment accepting unit 120 and is inapproximately “arm's-length” distance (e.g., 3 to 5 feet) of the paymentaccepting unit 120, the user could observe the transferred funds on thedisplay 122, 124 (FIG. 19) of the payment accepting unit 120. Thetransaction is completed just as if cash was inserted into the paymentaccepting unit 120 with the user inputting his/her selection on thepayment accepting unit 120 and the payment accepting unit 120 dispensingthe product or service. After the selection is made, the change isreturned to the mobile device 150. FIG. 3 details when the hands-freemode would be available.

Multiple Vending Transactions (Multi-Vend): Both the manual andhands-free modes could be used multiple times in sequence (implemented,for example, as a loop) so that a user may make multiple purchases.After making his/her first selection and receiving his product (orservice), the user would observe that additional funds were available onthe display 122, 124 (FIG. 19) on the payment accepting unit 120. He/shecould make another selection (or multiple selections) and receiveadditional product(s) (or service(s)). More specifically, the display122, 124 (FIG. 19) may reset as if the transaction is complete, butthen, because the user is still standing in range, the mobileapplication 140 would send another credit to the payment accepting unit120, allowing for a second purchase. When the user walks away, thesystem clears (e.g., returns unused funds to the application 140 on themobile device 150).

The features described above, alone or in combination with otherfeatures described herein will revolutionize the hundred billion dollarautomated retail industry. The hardware is very low cost and there areno reoccurring fees because no cellular connection is required on themachine 120. Using the mobile-device-to-machine payment processingsystem described herein, operators of machines 120 can increasefrequency of visits by purchasers and items sold with each visit.

The mobile-device-to-machine payment processing system described hereinmay be implemented as an apparatus, system, and/or method for enablingpayments to a machine 120 via a mobile device 150. Themobile-device-to-machine payment processing system may be betterunderstood with reference to the drawings, but the shownmobile-device-to-machine payment processing system is not intended to beof a limiting nature.

Definitions

Before describing the mobile-device-to-machine payment processing systemand the figures, some of the terminology should be clarified. Pleasenote that the terms and phrases may have additional definitions and/orexamples throughout the specification. Where otherwise not specificallydefined, words, phrases, and acronyms are given their ordinary meaningin the art. The following paragraphs provide some of the definitions forterms and phrases used herein.

Adapter Module 100: As shown in FIGS. 1 and 2, the adapter module 100(sometimes also herein called the “payment module 100”) is a physicaldevice that is installed in a machine 120 (a payment accepting unit120). The shown adapter module 100 is an in-line dongle (a hardwaredevice with software thereon) device that may be inserted in-line withina multi-drop bus (MDB) of a machine 120. The adapter module 100 bridgesthe communication between the machine 120 and a mobile device 150.Although described as a unique component, it should be noted that theadapter module 100 could be implemented as a plurality of devices orintegrated into other devices (e.g., components of a machine 120). Inits unique component form, the adapter module 100 can be easily insertedinto a machine 120 so that the machine 120 is able to perform newfeatures with the assistance of the adapter module 100. FIG. 20 showscomponents associated with the adapter module 100. As shown in FIG. 20,the communications unit 770 of the adapter module 100 includesshort-range communication capability 776 (e.g., Bluetooth mechanisms).The shown example may be divided into multiple distinct components thatare associated with each other or the example may be incorporated intoor drawn from other technology (e.g., a computer or a payment acceptingunit) as long as the components are associated with each other.

Mobile Device 150 and Application 140 (also referred to as a “mobileapplication,” “mobile app,” or “app”): In general, a mobile device 150may be a user's personal mobile device 150. The mobile device 150 (witha mobile application 140 thereon) acts as a communication bridge betweenthe adapter module 100 (associated with a payment accepting unit 120)and the server 130. The mobile device 150 and the application 140,however, are not “trusted” in that the communications (transmissions) itpasses are encrypted. Encrypted (secured) communications areundecipherable (unencryptable, unreadable, and/or unusable) by themobile device 150. This keeps the communications passed between theadapter module 100 and the server 130 secured and safe from hacking.Mobile devices include, but are not limited to smart phones, tablet orlaptop computers, or personal digital assistants (PDAs), smart cards, orother technology (e.g., a hardware-software combination) known or yet tobe discovered that has structure and/or capabilities similar to themobile devices described herein. The mobile device 150 preferably has anapplication (e.g., the application 140) running on it. The term “app” isused broadly to include any software program(s) capable of implementingthe features described herein. FIGS. 10A-10D show user interfaces forthe application 140 displayed by the mobile device 150. It should benoted that the phrase “mobile device” can be assumed to include therelevant app unless specifically stated otherwise. Similarly, it shouldbe noted that an “app” can be assumed to be running on an associatedmobile device unless specifically stated otherwise. FIG. 21 showscomponents associated with the mobile device 150. The shown example maybe divided into multiple distinct components that are associated witheach other or the example may be incorporated into or drawn from othertechnology (e.g., the cell phone itself) as long as the components areassociated with each other.

Payment Accepting Unit 120 (or Machine 120): A payment accepting unit120 (or the machine 120) is equipment that requires payment for thedispensing of an product and/or service. Payment accepting units 120 maybe vending machines, parking meters, toll booths, laundromat washers anddryers, arcade games, kiosks, photo booths, toll booths, transit ticketdispensing machines, and other known or yet to be discovered paymentaccepting units 120. Some payment accepting units 120 can acceptcashless payments (payments other than cash (paper currency and coins))by accepting payment from, for example, credit cards, debit cards, andmobile devices.

Network Connections: For purposes of this discussion, a persistentnetwork connection is a wired or wireless communications connection thatis ongoing (e.g., a dedicated connection, a dedicated online connection,and/or a hardwired connection) or accessible on demand (e.g., theability for the machine to make a temporary connection to a server orthe ability for the user to contact a server from his mobile device).Typically the persistent network connection has been conducted over“long-range communication technology” or “long-range communicationprotocol” (e.g., hardwired, telephone network technology, cellulartechnology (e.g., GSM, CDMA, or the like), Wi-Fi technology, wide areanetwork (WAN), local area network (LAN), or any wired or wirelesscommunication technology over the Internet that is known or yet to bediscovered). Traditionally, machines that accept payment other than cashrequire a persistent (ongoing or accessible on demand) connection to anetwork to facilitate payment. This is true for machines that accept,for example, credit cards and debit cards. The payment accepting units120 described herein do not require a traditional persistent networkconnection. The user's mobile device 150 acts as a communication bridgebetween the adapter module 100 and the server 130. Communicationsbetween user mobile devices 150 and the servers (e.g., a systemmanagement server 130 and/or a funding source server 160) take placeusing long-range communication technology. Communications between usermobile devices 150 and the adapter module 100 of the payment acceptingunit 120 take place using “short-range communication technology” or“short-range communication protocol” (e.g., Bluetooth (such as Bluetooth4.0, Bluetooth Smart, Bluetooth Low Energy (BLE)), near-fieldcommunication (NFC), Ultra Wideband (UWB), radio frequencyidentification (RFID), infrared wireless, induction wireless, or anywired or wireless technology that could be used to communicate a smalldistance (approximately a hundred feet or closer) that is known or yetto be discovered). Therefore, neither the adapter module 100 nor thepayment accepting unit 120 requires a traditional persistent long-rangewireless network connection. The communications technology shown in thefigures may be replaced with alternative like communications technologyand, therefore, specific shown communications technologies are not meantto be limiting. For example, Wi-Fi technology could be replaced withanother long-range communication technology.

Server: A server is the host processing server that may be operated bythe company running the payment processing system. For each user, theserver 130 preferably maintains at least one “virtual wallet” having atleast one “balance” (which can be $0) of designated funds for which theserver 130 keeps an accounting. The balance may represent, for example,“cash” or it may be a “promotional value” that represents funds that maybe spent under certain circumstances. If these funds begin to bedepleted, the user may be notified (e.g., via the application 140 on themobile device 150) that additional funds need to be designated and/ortransferred. Alternatively, funds from other sources (e.g., the fundingsource server 160) may be automatically transferred to restore apredetermined balance. The balance may also be increased based on apromotion (e.g., points earned or coupons). As shown in FIG. 22, theserver includes appropriate processors 950, memory 960 (which would keepan accounting of the user's balance in a manner similar to a gift card),and communication systems 970. As shown in FIG. 22, the communicationsunit 970 of the server 130 includes long-range communication capability972 (e.g., cellular technology and/or Wi-Fi mechanisms). The server 130also includes a security unit 955 for encrypting and decryptingmessages. The server 130 receives an authorization request (sometimesalso herein called an “AuthRequest”) from the adapter module 100 (via amobile device 150) and, if funds are available, returns an authorizationgrant (sometimes also herein called an “AuthGrant” or an “authorizationgrant token”) for funds. FIG. 22 shows components associated with theserver 130. The shown example may be divided into multiple distinctcomponents that are associated with each other or the example may beincorporated into or drawn from other technology (e.g., a computer or amain frame) as long as the components are associated with each other.

Advertise Presence: Each adapter module 100 advertises its presence bybroadcasting signals (advertising broadcast signals) to mobile devicesin the zones 102, 104, 106. Each adapter module 100 can listen to otheradapter modules' advertisements.

Received Signal Strength Indicator (RSSI): The adapter module 100 mayhave a self-calibrating signal strength to determine zone thresholds(e.g., a payment zone threshold and an authentication zone threshold).At the time the user selects an item (product or service) from thepayment accepting unit 120, the Received Signal Strength Indicator(RSSI) is logged. At this moment, it is presumed the user is within“arm's-length” (which may be a predetermined length approximating thedistance of a user standing in front of a machine for the purpose ofmaking a purchase) from the payment accepting unit 120. A mathematicalcomputation (i.e., In-Range Heuristics) is conducted to derive theoptimal RSSI threshold at which point payment should be triggered by anapplication 140 on a mobile device 150. The threshold may be paymentaccepting unit specific and can vary over a period of time. This optimalzone threshold is preferably reported to the mobile device 150 during aninitial handshake.

In-Range Heuristics: A mathematical computation that determines the RSSIthreshold to determine when a user is in the authorization zone 104and/or the payment zone 102. This computation can take intoconsideration numerous historical data points as well as transactionspecific information such as which the mobile device 150 is being used,payment accepting unit type, among other factors. Preferably the RSSI islogged while the user is making his selection (this is the one time inthe entire process that the user definitely will be “in range” (e.g.,they will be arm's length from the machine 120 because they arephysically interacting with the machine 120). The type of user mobiledevice 150, accelerometer data (e.g., is the user moving or stationary),and/or other information may also be logged while the user is making hisselection. The adapter module 100 can give a reference RSSI for thepayment zone 102 for the machine 120, and the application 140 can make a+/−adjustment based on the specific mobile device 150 on which it isinstalled. Over a period of time, the payment processing systemcontinues to improve itself based on additional data points.

Authorization Request (“AuthRequest:): When a user enters theauthorization zone 104, the mobile device 150 notifies the adaptermodule 100 and the adapter module 100 sends a secured authorizationrequest (e.g., the encrypted authorization request) as a “message” (alsoreferred to as a communication or transmissions) to the server 130 viathe mobile device 150. Encryption may be performed by a security unit755 (FIG. 20) with security technology (e.g., encryption and decryptionmeans) that may be associated with the processing unit 750 and/or thememory 760. Significantly, the AuthRequest is a request forauthorization of funds, not a request for authorization of atransaction. The purpose of the funds is irrelevant to the server 130.

Authorization Grant Token (“AuthGrant”): This is a “message” (alsoreferred to as a communication or transmissions) encrypted by thesecurity unit 955 (FIG. 22) with security technology (e.g., encryptionand decryption means) of the server 130 with the unique private keycorresponding to the adapter module 100. The secured authorization grant(e.g., the encrypted authorization grant) is passed from the server 130to the adapter module 100 via the mobile device 150 in the form of amessage. The mobile device 150, however, is not able to decrypt and/orread the message. The authorization grant is in response to theauthorization request. The amount of the funds granted by the AuthGrantmay be determined by factors including, but not limited to, the amountof funds available (or, if funds are not available, a mini-loan could begranted), a pre-authorized amount (e.g., set by the server, set by theuser during set-up, set by the funding source, or a standard amount),limited by time (e.g., only a certain amount per hour, or apredetermined amount at specific times of the day), limited to themaximum amount of an item on the machine (or enough for two or threeitems in the machine), or one or more of these and other factors.Significantly, the AuthGrant makes the funds available, but does notauthorize a transaction. The AuthGrant may have an associated expirationperiod in that it may expire if it is not used in a pre-determined timeperiod. The length of time before the AuthGrant expires may bedetermined by factors including, but not limited to, the trustworthinessof the user (e.g., the user has a long history with the paymentprocessing system or some known provider (e.g., credit card provider,bank, or credit union), the user has a good credit rating, or the userhas a large wallet balance), a pre-authorized time period (e.g., set bythe server, set by the user during set-up, set by the funding source, ora standard time period), limited by time (e.g., predetermined timeperiods at specific times of the day such as longer times duringbreakfast, lunch, and dinner), limited by the machine or the products orservices sold in the machine, limited by the number of other users nearthe machine (e.g., if it is a crowded machine, the AuthGrant may expirefaster), or one or more of these and other factors. The AuthGrantremains valid until it expires or some other event occurs to end itsvalidity (e.g., the user cancels it). This means that under normalcircumstances the mobile device 150 will hold the AuthGrant authorizinguse of funds for a pre-determined time period that will allow the usersufficient time to make a purchase. The authorized amount may beconsidered to be the “wallet balance” that is held in a virtual“wallet.”

Synchronization: Time may be synchronized to the adapter module 100 fromthe server 130. The server 130 sends time information with encryptedmessages and the adapter module 100 uses the time encoded in themessages for synchronization.

The mobile-device-to-machine payment processing system and componentsthereof may have associated hardware, software, and/or firmware (avariation, subset, or hybrid of hardware and/or software). The term“hardware” includes at least one “processing unit,” “processor,”“computer,” “programmable apparatus,” and/or other known or yet to bediscovered technology capable of executing instructions or steps (shownas the processing unit 750 in FIG. 20, the processing unit 850 in FIG.21, and the processing unit 950 in FIG. 22). The term “software”includes at least one “program,” “subprogram,” “series of instructions,”or other known or yet to be discovered hardware instructions orhardware-readable program code. Software may be loaded onto hardware (orfirmware) to produce a “machine,” such that the software executes on thehardware to create structures for implementing the functions describedherein. Further, the software may be loaded onto the hardware (orfirmware) so as to direct the mobile-device-to-machine paymentprocessing system (and components thereof) to function in a particularmanner described herein or to perform a series of operational steps asdescribed herein. “Hardware” such as the adapter module 100, the mobiledevice 150, and the payment accepting unit 120 may have software (e.g.,programs and apps) loaded thereon. The phrase “loaded onto the hardware”also includes being loaded into memory (shown as the memory 760 in FIG.20, the memory 860 in FIG. 21, and the memory 960 in FIG. 22) associatedwith or accessible by the hardware. The term “memory” is defined toinclude any type of hardware (or other technology)-readable media (alsoreferred to as computer-readable storage medium) including, but notlimited to, attached storage media (e.g., hard disk drives, network diskdrives, servers), internal storage media (e.g., RAM, ROM, EPROM,FLASH-EPROM, or any other memory chip or cartridge), removable storagemedia (e.g., CDs, DVDs, flash drives, memory cards, floppy disks,flexible disks), firmware, and/or other known or yet to be discoveredstorage media. Depending on its purpose, the memory may be transitoryand/or non-transitory. Appropriate “messages,” “communications,”“signals,” and/or “transmissions” (that includes various types ofinformation and/or instructions including, but not limited to, data,commands, bits, symbols, voltages, currents, electromagnetic waves,magnetic fields or particles, optical fields or particles, and/or anycombination thereof) over appropriate “communication paths,”“transmission paths,” and other means for signal transmission includingany type of connection between two elements on the payment processingsystem (e.g., the adapter module 100, the mobile device 150, the paymentaccepting unit 120, hardware systems and subsystems, and memory) wouldbe used as appropriate to facilitate controls and communications.

It should be noted that the terms “programs” and “subprograms” aredefined as a series of instructions that may be implemented as software(i.e. computer program instructions or computer-readable program code)that may be loaded onto a computer to produce a “machine,” such that theinstructions that execute on the computer create structures forimplementing the functions described herein or shown in the figures.Further, these programs and subprograms may be loaded onto a computer sothat they can direct the computer to function in a particular manner,such that the instructions produce an article of manufacture includinginstruction structures that implement the function specified in the flowchart block or blocks. The programs and subprograms may also be loadedonto a computer to cause a series of operational steps to be performedon or by the computer to produce a computer implemented process suchthat the instructions that execute on the computer provide steps forimplementing the functions specified in the flow chart block or blocks.The phrase “loaded onto a computer” also includes being loaded into thememory of the computer or a memory associated with or accessible by thecomputer. Separate, albeit interacting, programs and subprograms may beassociated with the adapter modules 100, the server 130, and the mobiledevice 150 (including the mobile application 140) and these programs andsubprograms may be divided into smaller subprograms to perform specificfunctions.

The terms “messages,” “communications,” “signals,” and/or“transmissions” include various types of information and/or instructionsincluding, but not limited to, data, commands, bits, symbols, voltages,currents, electromagnetic waves, magnetic fields or particles, opticalfields or particles, and/or any combination thereof. Appropriatetechnology may be used to implement the “communications,” “signals,”and/or “transmissions” including, for example, transmitters, receivers,and transceivers. “Communications,” “signals,” and/or “transmissions”described herein would use appropriate technology for their intendedpurpose. For example, hard-wired communications (e.g., wired serialcommunications) would use technology appropriate for hard-wiredcommunications, short-range communications (e.g., Bluetooth) would usetechnology appropriate for close communications, and long-rangecommunications (e.g., GSM, CDMA, Wi-Fi, or the like) would usetechnology appropriate for remote communications over a distance.Appropriate security (e.g., SSL or TLS) for each type of communicationis included herein. The security units 755 and 955 include technologyfor securing messages. The security technology may be, for example,encryption/decryption technology (e.g., software or hardware). Althoughencryption/decryption is discussed primarily as being performed using aunique private key, alternative strategies include, but are not limitedto encryption/decryption performed using public/private keys (i.e.,asymmetric cryptography), or other encryption/decryption strategiesknown or yet to be discovered. Appropriate input mechanisms and/oroutput mechanisms, even if not specifically described, are considered tobe part of the technology described herein. The communications unit 770(shown in FIG. 20) of the adapter module 100 is shown as includingappropriate input and output mechanisms 772, 774 that may be implementedin association (e.g., directly or indirectly in functionalcommunication) with male and female adapters 720, 730 of the adaptermodule 100. The communications unit 870 (shown in FIG. 21) of the mobiledevice 150 includes mechanisms for both long-range communications (shownas the long-range communication capability 872 such as cellular and/orWi-Fi mechanisms) for communicating with the server 130 and short-rangecommunications (shown as the short-range communication capability 876such as Bluetooth mechanisms) for communicating with the adapter module100.

When used in relation to “communications,” “signals,” and/or“transmissions,” the terms “provide” and “providing” (and variationsthereof) are meant to include standard means of provision including“transmit” and “transmitting,” but can also be used for non-traditionalprovisions as long as the “communications,” “signals,” and/or“transmissions” are “received” (that can also mean obtained). The terms“transmit” and “transmitting” (and variations thereof) are meant toinclude standard means of transmission, but can also be used fornon-traditional transmissions as long as the “communications,”“signals,” and/or “transmissions” are “sent.” The terms “receive” and“receiving” (and variations thereof) are meant to include standard meansof reception, but can also be used for non-traditional methods ofobtaining as long as the “communications,” “signals,” and/or“transmissions” are “obtained.”

The term “associated” is defined to mean integral or original,retrofitted, attached, connected (including functionally connected),positioned near, and/or accessible by. For example, if the userinterface (e.g., a traditional display 122 (FIG. 19), a touch screendisplay 124 (FIG. 19), a key pad 126 (FIG. 19), buttons 126 (FIG. 19,shown as part of the key pad 126), a keyboard (not shown), and/or otherinput or output mechanism) is associated with a payment accepting unit120, the user interface may be original to the payment accepting unit120, retrofitted into the payment accepting unit 120, attached to thepayment accepting unit 120, and/or a nearby the payment accepting unit120. Similarly, adapter modules 100 may be associated with paymentaccepting units 120 in that the adapter modules 100 may be original tothe payment accepting unit 120, retrofitted into the payment acceptingunit 120, attached to the payment accepting unit 120, and/or a nearbythe payment accepting unit 120.

System Overview

FIGS. 5, 6, and 7 together show major components of themobile-device-to-machine payment system and the interactionsthere-between.

As shown, the adapter module 100 functionally connected bi-directionallyto the payment accepting unit 120 via a wired serial connection suchthat no security is necessary. The adapter module 100 is alsofunctionally connected bi-directionally to the mobile device 150 (andits installed mobile application 140) via short-range communicationtechnology (e.g., a Bluetooth connection). Because the mobile device 150is not a “trusted” link (e.g., it could be hacked by a user), onlysecured communications (transmissions) are passed between the adaptermodule 100 and the mobile device 150. This keeps communications securedand safe from hacking. The mobile device 150 (and its installed mobileapplication 140) is also functionally connected bi-directionally to asystem management server 130 and/or a funding source server 160 vialong-range communication technology (e.g., Wi-Fi or Cellular connection)that preferably has appropriate security (e.g., SSL security). Securitybetween the mobile device 150 and the system management server 130 hasthe advantage of protecting communications from the mobile device 150 tothe system management server 130 that may include sensitive data and maynot be encrypted. The system management server 130 and the fundingsource server 160 may be connected via a wired Internet connection withSSL security. The system management server 130 may be connected via awired Internet connection with SSL security to an operators' server 170.Although not necessary to implement a purchase transaction, for otherpurposes (e.g., inventory), the operators' server 170 may be connectedto the payment accepting unit 120 using a handheld computer sync or acellular connection.

Also, a unique private key may be used to securely transmit encryptedmessages between the adapter module 100 and the system management server130 (although the encrypted transmissions would most likely be routedthrough the mobile device 150). The server 130 stores a private key foreach adapter module 100, and this key is only known to the adaptermodule 100 and the server 130. No intermediary is privy to this key(especially not the mobile device 150). When the adapter module 100 andthe server 130 communicate messages (e.g., AuthRequest and AuthGrant),the security unit 755 of the adapter module 100 encrypts the messagewith its private key and passes the message to the mobile device 150.The mobile device 150 (which preferably cannot decrypt the message)passes the encrypted message to the server 130. The server 130 is ableto decrypt the message using the security unit 955 of the adapter module100 and the unique private key. The security unit 955 of the server 130uses this same unique private key to encrypt messages to the adaptermodule 100 and sends the message to the mobile device 150 to relay tothe adapter module 100 that is able to decrypt the message using thesecurity unit 755 of the adapter module 100 and the unique private key.

FIG. 7 shows specific communications and messaging with a vendingsequence (the numbers to the left of the communications and messaging)between the adapter module 100, the mobile device 150, and the systemmanagement server 130. These communications are discussed in more detailin the discussion pertaining to the schematic flow diagrams (FIGS.8A-8G) and the flow charts (FIGS. 9A-9E).

It should be noted that FIGS. 5, 6, and 7 are examples, and are meant tohelp in the understanding of the mobile-device-to-machine paymentsystem. For example, the shown long-range communications technology maybe replaced with alternative long-range communications technology knownor yet to be discovered, the shown short-range communication technologymay be replaced with alternative short-range communication technologyknown or yet to be discovered, and the shown security may be replacedwith alternative security known or yet to be discovered. The shownconnections are meant to be examples, and there may be intermediariesthat are not shown. The shown components have been simplified in that,for example, only one mobile device 150 (or machine 120, adapter module100, or server 130) is shown where many may be included. Finally, theorder of the steps may be changed and some steps may be eliminated.

Adapter Module

FIGS. 11-18 show views of adapter module 100 a (referred to generally asadapter module 100). Adapter module 100 is a relatively low costhardware component that is pre-configured to work with the industrystandard multi-drop bus (MDB). On machines without MDB technology, theadapter module 100 can be configured or designed to work with otherserial protocols or activate a switch. In essence the adapter module 100simulates establishing payment on payment accepting unit 120 in much thesame manner as other alternative forms of payment (e.g., cash).

The shown adapter modules 100 are preferably designed to be used as anin-line dongle for in-line insertion within, for example, a MDB of amachine 120. The wire used in MDB technology uses male and femaleconnection ends or adapters to allow the attachment of peripherals. Inthe case of a vending machine, the wire with the connection ends oradapters would be present to allow the attachment of a payment receivingmechanism (e.g., a coin mechanism). The MDB male and female adapters700, 710 may be separated (as shown in FIGS. 17-18). The adapter module100 a in FIGS. 11 and 17-18 has a male adapter 720 and a female adapter730. The adapter module 100 a may be plugged (inserted) in serial(“in-line”) with the wire. For example, the MDB female adapter 710 maybe connected to the male adapter 720 of the adapter module 100 and theMDB male adapter 700 may be connected to the female adapter 730 of theadapter module 100. The resulting in-line configuration is shown in FIG.19. It should be noted that the adapter modules 100 are designed toallow pass-through communications so that if themobile-device-to-machine payment processing system is not enabled (e.g.,for a particular purchase or simply turned off) the MDB functions asthough the adapter module 100 is not there and the machine 120 canfunction normally.

Hands-Free Mode

Summarily, if it is available, a hands-free mode, from the user'sperspective, would allow the user to approach a favorite paymentaccepting unit 120 and notice that the display (e.g., the displays 122or 124 shown in FIG. 19) associated with the payment accepting unit 120shows funds available (e.g., the wallet balance), he would select theproduct or service using input mechanisms (e.g., buttons 126 or a touchscreen display 124 shown in FIG. 19) associated with the paymentaccepting unit 120, and he would retrieve his dispensed services orproducts.

During an initial handshake with the mobile device 150 (when the user iswithin range), the adapter module 100 reports to the mobile device 150whether or not hands-free mode is available. If it is available, theinstalled mobile application 140 automatically connects to the paymentaccepting unit 120 without the user having to interact with the mobiledevice 150. The user observes that funds are available on the display122, 124 of the payment accepting unit 120 and completes the purchasetransaction as if cash was inserted in the machine 120 by inputting hisselection on the payment accepting unit 120. The payment accepting unit120 dispenses the product or service. After the selection is made, thechange is returned to the mobile device 150.

Whether hands-free payment is available is determined by factorsincluding, but not limited to whether if other mobile devices 150 are inrange, if other adapter modules 100 are in range, if there are anyalerts, if the payment trigger threshold is having wide variances and sodeemed unstable, or if the payment accepting unit operator (e.g., avending machine operator) has opted to disable hands-free mode for thepayment accepting unit 120. In the latter instance, operators candisable via a maintenance mobile device 150, as well as through theoperators' server 170 and/or the system management server 130.

FIG. 3 is a table that shows considerations, conditions, or factors thatmay be used to determine whether the hands-free pay feature isavailable. Starting at the “Favorite?” column, this indicates whetherthe payment accepting unit 120 is a favorite machine. Preferably thehands-free pay feature is only available for use with “favorite” paymentaccepting units 120 (e.g., a vending machine at work or school). The“Alert” column has to do with whether there is some reason (e.g., thereare too many users in range) that the hands-free pay feature should notwork and, if there is such a reason, the user will be notified (alerted)and may be able to use the manual mode to resolve the alert and/orcomplete the transaction. FIG. 3 shows situations in which a user is oris not able to make hands-free purchases from a machine 120 using amobile application 140 on his mobile device 150. It should be noted thatthe shown interface is an example. For example, some of the featurescould be automated or pre-selected. (It should be noted that the lefthand column, the “Tab” column, relates to whether the selected tab onthe mobile application 140 is “all” or “favorite.” FIGS. 10A-10D allshow these tabs. Unlike the other columns in FIG. 3, this column hasmore to do with the functionality and view of the application 140 thanspecifically with the hands-free feature. The tabs would allow a user toselect whether he wanted to be alerted when he was in range of allpayment accepting units 120 or just “favorite” payment accepting units120 and the application 140 would show the appropriate view.)

Balance Display: An optional feature of the mobile-device-to-machinepayment system that is particularly helpful in the hands-free mode(although it may be available in the manual mode and/or in amultiple-vend scenarios) is when the user's mobile device 150 sends“credit” to the payment accepting unit 120 (either via hands-freepayment or through a manual swipe), the wallet balance is sent to thepayment accepting unit 120 that is then displayed to the user on adisplay 122, 124 of the machine 120. This is particularly beneficialduring hands-free mode when the user does not retrieve the mobile device150 and, therefore, may not know the balance. Also, in a multiple-vendscenario the user would not have to calculate a remaining balance.

An example of a hands-free, multiple-vend scenario where a balance isdisplayed by the payment accepting unit 120, follows: The user has $5.00in his/her virtual wallet as that is the amount that has been authorized(the AuthGrant being stored on the mobile device 150). The user walks upto the payment accepting unit 120 and $5.00 is displayed on the display122, 124 of the payment accepting unit 120 since hands-free mode wasenabled and credit was sent (e.g., via the short-range communicationcapability) to the payment accepting unit 120. The user makes aselection of $1.50 by interacting (e.g., pressing buttons) with themachine 120. The item (product or service) is dispensed and the “change”is “returned” (e.g., via the short-range communication capability) tothe virtual wallet. But since the user is still standing in the paymentzone 102, the remaining wallet balance of $3.50 is sent to the paymentaccepting unit 120 and displayed so that the user can now see thathe/she has a $3.50 balance. (It should be noted that the authorizedfunds may remain on the machine 120 and not be transferred back to themobile device 150 between transactions.) The user decides to purchase a$1.50 item, and the transaction is completed as usual (e.g., byinteracting with the machine 120). Now the user is still standing in thepayment zone 102 and he/she sees the wallet balance of $2.00 on thedisplay 122, 124 of the payment accepting unit 120. The user decidesthat he/she does not wish to purchase anything else and simply walksaway. As he/she walks out of the payment zone 102, the credit is clearedfrom the machine 120, but he/she is left with the knowledge that hiswallet balance is $2.00 even though he/she never touched the mobiledevice 150. Communications between the payment accepting unit 120 andthe adapter module 100 (via the mobile device 150) handle the accountingincidental to the transaction. The remaining balance ($2.00) istechnically stored on the server 130, and may be reflected on theapplication 140 on the mobile device 150.

Multiple Distinct Zones

As shown in FIGS. 1-2, the functions performed by the adapter module 100can be divided into distinct zones: a first “communication zone” (e.g.,“Bluetooth range” 106), a second “authorization zone” 104, and a third“payment zone” 102. The payment zone 102 is smaller than or equal to(overlapping completely) the authorization zone 104. Put another way,the payment zone 102 is within or coextensive with the authorizationzone 104. The payment zone 102 is a subset of the authorization zone 104with a ratio of the payment zone 102 to the authorization zone 104ranging from 0.01:1 to 1:1. It is not necessarily a fixed ratio and canvary between different payment accepting units 120, different mobiledevices 150, different users, and over time. While the zones 102, 104,106 are depicted as having a uniform shape, the zones may notnecessarily be uniform (or constant over time) in that the shape canvary. For example, the shape of the Bluetooth range 106 may varydepending on environmental conditions such as obstacles in the room andpayment accepting unit 120 door/wall materials.

Bluetooth Range 106 (sometimes also herein called the “communicationzone”): The outermost range is the Bluetooth range 106 (shown in FIGS.1-2). This is the area in which the adapter module 100 is able tobroadcast its presence. In most situations, the Bluetooth range 106 is apassive range in that no actual data is exchanged between the mobiledevice 150 and the adapter module 100. While in the Bluetooth range 106,the mobile device 150 monitors the RSSI (Received Signal StrengthIndicator).

Authorization Zone 104: The middle region is the authorization zone 104(shown in FIGS. 1-2). This is a computed area based on the RSSI. Asmentioned, the mobile device 150 monitors the RSSI while it is in theBluetooth range 106. When the RSSI reaches a certain predeterminedthreshold based on In-Range Heuristics, the mobile device 150 can beconsidered to be in the authorization zone 104. In the authorizationzone 104 the mobile device 150 establishes a connection to the adaptermodule 100 (e.g., a Bluetooth connection (FIG. 5) with SSL protection(FIG. 6)) and informs the adapter module 100 of its presence. After asuccessful handshake with the adapter module 100, the mobile device 150registers the adapter module 100 and the adapter module 100 requests anauthorization to the server 130 via the mobile devices' networkconnection (e.g., a Wi-Fi or cellular connection (FIG. 5) with SSLprotection (FIG. 6)). It is important to note the mobile device 150 andthe adapter module 100 have a non-exclusive relationship at this point.The adapter module 100 may collect registrations for all mobile devices150 that are within the authorization zone 104.

An authorization occurs in preparation for when the user enters thepayment zone 102 (shown in FIGS. 1-2). An authorization expires in a setperiod of time (for example, five minutes), so if the mobile device 150is still in the authorization zone 104 at the time of expiration, theadapter module 100 submits for and receives another authorization. Thiswill continue for a set number of times (for example, the limit may bethree times to limit cases of numerous authorizations for a mobiledevice that may remain in the authorization zone 104 for an extendedperiod of time without completing a transaction). Should authorizationfail (for instance if the limit had been reached) prior to the userentering the payment zone 102, the adapter module 100 will requestauthorization when the mobile device 150 enters the payment zone 102(which adds a few seconds to the experience).

Payment Zone 102: As a user enters the payment zone 102, the mobiledevice 150 establishes exclusive control of the adapter module 100. Onceestablished, any other user in the payment zone 102 is put into a“waiting” status.

In the payment zone 102, the payment can be triggered automatically ifthe payment processing system has and is in hands-free mode. In suchinstances, the mobile device 150 is running the application 140 inbackground mode and will send credit to the payment accepting unit 120without any explicit user interaction. The user completes thetransaction on the payment accepting unit 120 in much the same manner asif cash had been inserted into the payment accepting unit 120 toestablish credit. After the user completes the transaction (that mayinclude one or more purchases), details of the transaction arepreferably returned to the mobile device 150 and server 130 in separatemessages. The message to the server 130 is preferably encrypted with theadapter module's 100 private key (FIG. 6) to ensure data integrity. Asshown in FIG. 7, the “private key” coded message (Encrypted VendDetails)is preferably sent via the mobile device 150. The message to the mobiledevice 150 may be sent solely for the purpose of closing thetransaction. The transaction history and balance are updated server-sidevia the encrypted message sent to the server 130.

The other mode of operation is manual mode. In manual mode, the userlaunches the mobile device 150 and is able to swipe to send payment tothe payment accepting unit 120. The user can also swipe back to cancelthe payment. Like in hands-free mode, the purchase transaction iscompleted on the payment accepting unit 120 in the same manner as ifcash were inserted into the payment accepting unit 120. The mobiledevice 150 is only used to send payment. Selection is made directly onthe payment accepting unit 120.

Self-Calibrating Zone Threshold: A key, but optional feature, of thepayment processing system is a self-calibrating payment zone RSSIthreshold. Because RSSI can vary machine to machine, environment toenvironment, and device to device, having a fixed threshold at whichpayment is triggered can be problematic. The approach suggested hereinis the creation of a self-calibrating threshold. When the user isinteracting with the payment accepting unit 120 (such as when he makeshis selection on the payment accepting unit 120), the payment acceptingunit 120 notifies the adapter module 100 and the adapter module 100 logsthe conditions such as RSSI, type of user mobile device 150,accelerometer data, and other information. It is at this point that itcan be ascertained safely that the user is within arm's-length from thepayment accepting unit 120 (by necessity the user is arm's-lengthbecause he is making some physical interaction with the paymentaccepting unit 120). This is the only point in the entire transaction inwhich it can be certain that the user is within arm's-length from thepayment accepting unit 120.

FIG. 4 shows a simplified set of steps involved when users enter thepayment zone 102. Specifically, FIG. 4 shows that credit is established200 (this may have been done in the authorization zone 104, but if notit would be handled in the payment zone 102), that the user makes aselection using the machine 202, that the machine notifies the adaptermodule of the selection 204, that the adapter module (optionally) logsthe RSSI 206, and that the purchase process(es) continues 208. Using thehistorically logged RSSI data, the adapter module 100 calculates one ofseveral “average” RSSI using various mathematical models. This “average”could be a traditional average, a moving average, a weighted average, amedian, or other similar summary function. The adapter module 100 couldpre-process the historical data before running the function, such as toeliminate top and bottom data points, suspect data points, etc.

Optionally, during the handshake between the mobile device 150 and theadapter module 100, the information transmitted to the adapter module100 may include, for example, the model of the mobile device 150. Usingthe received information pertaining to the mobile device models, theadapter module 100 can create multiple payment thresholds, one for eachmobile device model. This allows for variances that may be inherent indifferent types of Bluetooth radios. An alternative to this method isfor the adapter module 100 to broadcast a baseline payment zonethreshold, and the mobile device 150 can use an offset from thisbaseline based on its specific model type. The payment zone thresholds(or baseline offsets) can be unique to specific types of mobile devices(e.g., by manufacturer, operating system, or component parts), models ofmobile devices, or individual mobile devices (unique to each user).

In a typical scenario in which the payment zone threshold has beencalibrated, the adapter module 100 advertises its presence along withthe threshold at which it considers any mobile device 150 to be in theauthorization zone 104. This is a one-way communication from adaptermodule 100 to mobile device 150. Once the mobile device 150 enters theauthorization zone 104, there is a handshake that is established betweenthe adapter module 100 and the mobile device 150. During this handshake,the mobile device 150 can share its model information with the adaptermodule 100, and the adapter module 100 can return the payment zone 102threshold for that specific model.

Optionally, in addition to calibrating the payment zone threshold, theadapter module 100 can apply the self-calibrating model to theauthorization zone 104 to calibrate the authorization zone threshold. Aswith the payment zone thresholds, the authorization zone thresholds canbe unique to specific types of mobile devices, models of mobile devices,or individual mobile devices. In this scenario, the adapter module 100would broadcast multiple thresholds by device type and the mobile device150 would determine which threshold to apply (or alternatively broadcasta baseline and the mobile device 150 uses an offset based on its devicemodel). Even in this scenario, the authorization zone 104 is a one-waycommunication.

Optionally, along with the threshold that is calculated (in the paymentand/or the authorization zone(s)), a safety margin can be added tominimize scenarios in which a user is within range, but themobile-device-to-machine payment processing system does not recognize itbecause the threshold may not have been reached. For example, if thecalculated RSSI for an iPhone™ 5 on machine 4567 is −68 db, themobile-device-to-machine payment processing system may add a safetymargin of −5 db, and establish the threshold at −73 db. So when a user'sphone is communicating with the adapter module 100 at an RSSI of −73 dbor better, the mobile-device-to-machine payment processing system willallow the mobile device 150 to credit the payment accepting unit 120.The safety margin can be set on the server 130 and downloaded to theadapter module 100, or set on the mobile device 150, or set on theadapter module 100 itself.

Optionally, in the payment zone threshold, the mobile device 150 can useother data to determine when to cancel the exclusive control of thepayment accepting unit 120, to identify when the user is moving out ofthe payment zone 102. External data could include accelerometer datafrom the mobile device 150. Using that data, the mobile device 150 candetermine whether the user is standing relatively still in front of thepayment accepting unit 120, or if the user is in motion—effectivelywalking away from the payment accepting unit 120.

Signal Unavailability Adaptation

The mobile-device-to-machine payment processing system described hereinuses a mobile device's 150 short-range communication technology (e.g.,Bluetooth mechanisms) (shown as short-range communication capability 876in FIG. 21) and a mobile device's 150 long-range communicationstechnology (e.g., cellular and/or Wi-Fi mechanisms) (shown as long-rangecommunication capability 872 in FIG. 21). The short-range communicationcapability 876 communicates with the adapter module's 100 short-rangecommunication technology (e.g., Bluetooth mechanisms) (shown asshort-range communication capability 776 in FIG. 20). The long-rangecommunication capability 872 communicates with the server's 130long-range communications technology (e.g., cellular and/or Wi-Fimechanisms) (shown as long-range communication capability 972 in FIG.22). The mobile device 150 (with a mobile application 140 thereon) actsas a communication bridge between the adapter module 100 (associatedwith a payment accepting unit 120) and the server 130. This process isdescribed herein and works properly if there is cellular or Wi-Ficoverage within the payment zone 102.

One option if there is no cellular or Wi-Fi coverage within the paymentzone 102 is to determine whether there is cellular or Wi-Fi coveragewithin the authorization zone 104 or the Bluetooth range 106. If thereis, then the sizes of the zones 102, 104, 106 could be adapted and thetiming could be adapted. For example, if the mobile devices 150 detectedproblems with the cellular or Wi-Fi coverage within the payment zone102, the user could carry his mobile device 150 into the other zones (orthe mobile device 150 could use short-range communication technology tocommunicate with other mobile devices 150 within the authorization zone104 or the Bluetooth range 106) to determine whether the zones havecellular or Wi-Fi coverage. If they do have coverage, communicationbetween the mobile device 150 and the server 130 can be advanced(conducted earlier when the mobile device 150 is further from themachine 120) or delayed (conducted later when the mobile device 150 isfurther from the machine 120). This can be thought of as changing thesize or shapes of the zones 102, 104, 106. The timing would also have tobe adjusted so that the authorization of funds (AuthGrant) does notexpire before the user has a chance to make a purchase. It also meansthat balance updates to the server 130 may happen after the user hasmoved away from the machine 120 and has cellular or Wi-Fi coverageagain.

Another option if there is no cellular or Wi-Fi coverage within any ofthe zones 102, 104, 106 is for the user to obtain authorization whileoutside of the zones in a place with cellular or Wi-Fi coverage. Thismay occur, for example, if a user knows that he will be going to a placewith a payment accepting unit 120 equipped with an adapter module 100(perhaps to a favorite payment accepting unit 120) that does not have(or rarely has) cellular or Wi-Fi coverage. A user may also use themobile application 140 to query payment accepting units 120 in a givenrange (e.g., within 50 miles) or at a given location (e.g., at acampground or in a particular remote city) to determine whether there iscellular or Wi-Fi coverage within the zones 102, 104, 106. The user canthen obtain pre-authorization from the server 130 using the mobileapplication 140. Again, the timing would also have to be adjusted sothat the authorization of funds (AuthGrant) does not expire before theuser has a chance to make a purchase. It also means that balance updatesto the server 130 may happen after the user has moved away from themachine 120 and has cellular or Wi-Fi coverage again. Amobile-device-to-machine payment system having the ability to implementthis option would be able to accept cashless payments without requiringany network connection near the payment accepting unit 120. In someimplementations, the mobile-device-to-machine payment processing systemsdescribed herein is located in a remote location where no signal isavailable, therefore, can accept cashless payments.

As an example of a situation in which there might be no cellular orWi-Fi coverage within any of the zones 102, 104, 106 of a particularpayment accepting unit 120, the user (a teenager) may be traveling to aremote location to attend summer camp where there is no cellular orWi-Fi coverage. The camp may have several payment accepting units 120(e.g., a machine that creates a dedicated “hot spot” that requirespayment for use, vending machines, or machines for renting equipmentsuch as bikes, kayaks, or basketballs). The camp facility might notifyparents that the mobile-device-to-machine payment system is available.The parents, while at home, could obtain authorization for a particularamount (that could be doled out a certain amount per day or limited totype of machine or location) to be authorized and “loaded” into theuser's mobile device 150 and specify that the authorization will notexpire for a certain period or until a certain date. Thereafter, whileat camp, the user could use the mobile application 140 on his mobiledevice 150 in a manner similar to those discussed elsewhere herein.Short-range communications may be used for communications between theadapter modules 100 (associated with the machines 120) and users' mobiledevices 150.

One subtle but powerful component of the payment processing systemdescribed herein is that it requires a long-range communicationcapability (e.g., an Internet or cellular network connection) only inthe authorization zone 104 and only for the time period required to sendthe AuthRequest and receive the AuthGrant. Once a valid AuthGrant isreceived by the mobile device 150, the long-range communicationcapability (e.g., an Internet or cellular network connection) is notrequired by either the mobile device 150 or the adapter module 100 inthe payment zone 102 as long as the AuthGrant is valid (unexpired). Thismechanism allows the system to seamlessly handle authenticatedtransactions in (temporary) offline mode, with the deferredacknowledgement and transaction messages performing the bookkeeping andcleanup when network connection is regained. The alternatives describedabove provide a unique way to artificially extend the authorization zoneto include any location where the mobile device 150 can communicate withthe server 130.

Multiple User Resolution

As shown in FIG. 2, in one practical scenario, multiple users are in thezones 102, 104, 106. As shown in FIG. 2, users 1, 2, and 3 are in thepayment zone 102 near the machine 120; users 5 and 6 are shown aspositioned between the authorization zone 104 and the Bluetooth range106; users 4 and 7 are in the Bluetooth range 106, user 10 is positionedon the edge of the Bluetooth range 106; and users 8 and 9 are positionedoutside of Bluetooth range 106. In some implementations, themobile-device-to-machine payment processing system manages and resolvesissues pertaining to multiple users.

Users 4 and 7 are within the Bluetooth range 106 and the user 10 iseither entering or leaving the Bluetooth range 106. Within the Bluetoothrange 106 the users' mobile devices 150 are able to see the adaptermodule's 100 advertisement. In this zone, the mobile device 150preferably does not initiate a connection. The adapter module 100 ispreferably unaware of the users in the Bluetooth range 106. All theadapter module 100 is doing is advertising its presence to any multitudeof users that may be in Bluetooth range 106.

The adapter module 100 begins to log users as the users (and theirrespective mobile devices 150) enter the authorization zone 104 (shownin FIG. 2 as users 5 and 6). At this point, there is a non-exclusiveconnection initiated by the mobile device 150 to the adapter module 100.It does a handshake (e.g., to exchange information needed to obtainauthorization and, optionally, to log information needed for aself-calibrating authorization zone threshold) and the mobile device 150contacts the server 130 for an authorization (e.g., sending anAuthRequest and receiving an AuthGrant). The adapter module 100registers all mobile devices 150 that have requested and receivedAuthGrants. The adapter module 100 continues communicating with anyother mobile device 150 that enters the authorization zone 104. Afterinitial contact, the adapter module 100 may provide the mobile device150 with a deferral delay of when to check back in with the adaptermodule 100 allowing opportunity for other mobile devices 150 tocommunicate with the adapter module 100.

If there is only one user in the payment zone 102, a purchasetransaction may be performed. If there are multiple users in the paymentzone 102, the mobile-device-to-machine payment system must handle thesituation.

One optional solution for handling the situation of the multiple usersin the payment zone 102 is queuing users in the payment zone 102. Onceany mobile device 150 enters the payment zone 102, it establishesexclusivity to a particular mobile device 150 (e.g., in afirst-come-first-serve manner). Technically, however, the adapter module100 is not establishing an exclusive connection to the mobile device150. The adapter module 100 can still perform a round-robin poll andcommunicate with and advertise to other mobile devices 150. Instead, theadapter module 100 establishes a queue prioritized by RSSI and time(e.g., who was first and whether the authorization has expired) and itnotifies (e.g., alerts) other mobile devices 150 to wait. The earliestvalid (unexpired) authorization takes precedence when there is any tiein the RSSI. Otherwise, for example, the strongest average RSSI takespriority. Preferably the queue is not a static measure of the RSSI butan averaged measure over the period of time in the queue. Thiscompensates for a scenario in which a user may be walking around in thequeue and then shows up at the payment accepting unit 120 just as theprevious user is finishing. If another user was also in the payment zone102 and stood there the entire time, but may have newer authorization,he could win out.

Anytime that the adapter module 100 cannot determine exactly which useris in the payment zone 102 in front of the payment accepting unit 120,the adapter module 100 will disable hands-free payment. The mobiledevice 150 will send an alert to the user and he can use swipe to pay(manual mode). All users in payment zone 102 will show “Connected” andthe first to swipe payment to the payment accepting unit 120 then locksout other users.

Multiple Module Resolution

In the scenario where there are multiple modules present, determiningwhich payment accepting unit 120 a user is in front of can be achallenge. In some implementations, the mobile-device-to-machine paymentprocessing system described herein allows adapter modules 100 tocommunicate to other adapter modules 100 in range via Bluetooth. Eachuser receives authorization grants for specific payment accepting units120. This means if there are multiple adapter modules 100 within thesame authorization zone 104, there will be multiple authorization grantsfor the user. When the user enters the payment zone 102, it can bedifficult to differentiate which payment accepting unit 120 the user isin front of if the payment zones 102 overlap.

To solve this problem, when the user enters the payment zone 102, theadapter modules 100 communicate with each other to determine the RSSIfor the particular user (based on the signal from his mobile device 150)to triangulate which adapter module 100 (and the associated paymentaccepting unit 120) is closer to the user. Optionally, the inter-modulecommunications can restrict the user to establishing an exclusiveconnection with only one payment accepting unit 120.

Optionally, when the user connects to a payment accepting unit 120, themobile device 150 can send a communication to the payment accepting unit120 for momentary display to the user on the display 122, 124 of thepayment accepting unit 120. For example, the mobile device 150 can senda communication (e.g., “connected” or “Fred's Mobile Device Connected”)to the payment accepting unit's display 122, 124 for a predeterminedperiod of time (e.g., 1-3 seconds) so when the user is in payment zone102, it is clear which payment accepting unit 120 the user is connectedto prior to making a purchase (either in hands-free or manual mode).

In addition, when the user is in manual mode, the mobile device 150 candisplay (e.g., on the touch screen 152 as shown in FIGS. 10A-10D) avisual indication of the payment accepting unit 120 (e.g., a pictureand/or a payment accepting unit ID of the payment accepting unit 120)for visual confirmation. If the user is in manual mode, the user canmanually change the payment accepting unit 120.

Descriptive Scenario

FIG. 7, FIGS. 8A-8G, and 9A-9E (as well as other figures) can be used tounderstand a detailed scenario of the mobile-device-to-machine paymentprocessing system described herein. A flow of communications and stepsare loosely described below with reference to these (and other figures).It should be noted that alternative scenarios could include, forexample, a modified order of the steps performed.

Prior to vending transactions, a user downloads a mobile application 140onto his mobile device 150, creates an account, and configures a fundingsource via, for example, a funding source server 160. A funding sourcemay be, for example, a debit card, a credit card, campus cards, rewardspoints, bank accounts, payment services (e.g., PayPal™) or other paymentoption or combination of payment options known or yet to be discovered.The funding sources may be traditional and/or nontraditional paymentsources that are integrated into the ecosystem described herein and thenused indirectly as a source of funds. Funds from the funding source arepreferably held on the server 130 such that when an AuthRequest isreceived by the server 130, the server 130 can send an AuthGrantauthorizing funds for a purchase.

The user can specify one or more “favorite” adapter module(s) 100 (thathas a one-to-one relationship to the payment accepting unit 120) that hemay visit regularly, such as a vending machine at school or work.Favorite adapter modules 100 appear on a pre-filtered list and allow foradditional rich features such as hands-free payment.

The payment accepting unit 120 may be equipped with an adapter module100 that is constantly advertising its availability via Bluetooth (orother “signals,” “communications,” and/or “transmissions”). This ongoingadvertising and scanning for adapter modules is shown in FIG. 8A. Asshown, the mobile device 150 is continuously scanning for any adaptermodule 100 within Bluetooth (or other “signal,” “communication,” and/or“transmission”) range. When the user is within range of that adaptermodule 100, the mobile device 150 tracks and monitors the signalstrength until a predetermined “authorization zone” threshold isachieved.

FIGS. 8B and 9A generally show that when the authorization zonethreshold is reached, the mobile device 150 enters the authorizationzone (block 302) and registers the adapter module 100. The mobile device150 connects to the server 130 (block 304). The application 140 on themobile device 150 creates a request for authorization (AuthRequest) andpasses the AuthRequest to the server 130 using appropriate communicationtechnology (e.g., GSM, CDMA, Wi-Fi, or the like) (block 306). The server130 responds with an authorization grant (AuthGrant) encrypted with thespecific adapter module's private key (block 306). This authorizationtoken may minimally include the User identifier (ID), Apparatus ID (forthe adapter module 100), authorization amount, and expiration time. Themobile device 150 receives the AuthGrant from the server 130, andretains it until the mobile device 150 is ready to issue payment to anadapter module 100. The mobile device 150 collects all pendingAuthGrants that may be one or more depending on how many adapter modules100 are in-range. Unused AuthGrants that expire are purged from themobile device 150 and the server 130. It is important to note that themobile device 150 is unable to read the AuthGrant because it isencrypted with the adapter module's unique private key that is onlyknown to server 130 and adapter module 100. This provides a preferredkey element of security in the system as the adapter module 100 onlytrusts AuthGrants that are issued by the server 130, and the AuthGrantscannot be read or modified by the mobile device 150 or any other partyin between the server and the adapter module 100. Additional mobiledevices 150 may enter the authorization zone 104 (block 308).

As the user approaches a specific adapter module 100, the user entersthe payment zone 102 and an event threshold is triggered based onheuristics performed by the mobile device 150. Blocks 310 and 312 showthe loop steps of waiting for a mobile device 150 from the authorizationzone 104 to enter the payment zone 102. If the user leaves theauthorization zone 104 without entering the payment zone 102, theadapter module 100 returns to advertising its presence (block 300).

FIGS. 8C and 9B generally show the user entering the payment zone. Themobile device 150 verifies that it has an unexpired and valid AuthGrant.If the AuthGrant is not good, it may be requested again, repeating theAuthorization Request process (block 315). If the AuthGrant is good, themobile device 150 sends the valid AuthGrant (including the walletbalance (block 322)) to the adapter module 100 to initiate atransaction. The mobile device 150 may issue the AuthGrant automaticallywithout specific user interaction if the hands-free mode is supported(and the device is a favorite (block 318), there is only one device inthe payment zone 102 (block 318), and (optionally) there is only oneuser in the authorization zone 104 (block 320). If any of these factorsare not present, the mobile device 150 will prompt and/or wait for theuser to begin the transaction manually (block 324).

FIGS. 8D, 9C, and 9D generally show the transaction process. As shown inFIG. 9C, the adapter module 100 runs through a series of questions todetermine if there are any issues that would prevent vending including:has the user canceled in-app? (block 326), has the user walked away?(block 328), is the coin return pressed? (block 330), has more than apredetermined period of time elapsed? (block 332). If the answer to anyof these questions is “yes,” the transaction does not proceed. If theanswers to all of these questions is “no,” the user makes a selection(block 334) on the payment accepting unit 120 in the same or similarmanner as compared to if cash or credit were presented to the paymentaccepting unit 120. If the machine 120 is able to vend (block 336), itattempts to release the product. If the vend fails (block 338) it isreported by the machine (block 340) and a credit is returned to thevirtual wallet (block 342). If the vend is successful (block 338) it isreported by the machine (block 344). Put another way, after thetransaction is complete, the adapter module 100 returns to the mobiledevice 150 the details of the transaction as well as an encrypted packetcontaining the vend details to be sent to the server 130 via the mobiledevice 150. Optionally, the adapter module 100 can pass additionalinformation not directly related to the transaction such as paymentaccepting unit health, sales data, error codes, etc.

FIGS. 8D and 9E generally show the multi-vend function. If the machinehas enabled multi-vend capabilities (block 350) and the multi-vend limithas not been reached, the process returns to the question of whether theuser is in the payment zone (block 310 of FIG. 9A). If the machine doesnot have enabled multi-vend capabilities (block 350) or the multi-vendlimit has been reached, the wallet is decremented by the vend amount(s)and “change” is returned to the virtual wallet (block 354) and theprocess ends (block 356).

FIG. 8E is a schematic flow diagram of an example login process. FIG. 8Fis a schematic flow diagram of an example boot-up process. FIG. 8G is aschematic flow diagram of an example account check/update process.

Several of the figures are flow charts (e.g., FIGS. 9A-9E) illustratingmethods and systems. It will be understood that each block of these flowcharts, components of all or some of the blocks of these flow charts,and/or combinations of blocks in these flow charts, may be implementedby software (e.g., coding, software, computer program instructions,software programs, subprograms, or other series of computer-executableor processor-executable instructions), by hardware (e.g., processors,memory), by firmware, and/or a combination of these forms. As anexample, in the case of software, computer program instructions(computer-readable program code) may be loaded onto a computer toproduce a machine, such that the instructions that execute on thecomputer create structures for implementing the functions specified inthe flow chart block or blocks. These computer program instructions mayalso be stored in a memory that can direct a computer to function in aparticular manner, such that the instructions stored in the memoryproduce an article of manufacture including instruction structures thatimplement the function specified in the flow chart block or blocks. Thecomputer program instructions may also be loaded onto a computer tocause a series of operational steps to be performed on or by thecomputer to produce a computer implemented process such that theinstructions that execute on the computer provide steps for implementingthe functions specified in the flow chart block or blocks. Accordingly,blocks of the flow charts support combinations of steps, structures,and/or modules for performing the specified functions. It will also beunderstood that each block of the flow charts, and combinations ofblocks in the flow charts, may be divided and/or joined with otherblocks of the flow charts without affecting the scope of the invention.This may result, for example, in computer-readable program code beingstored in whole on a single memory, or various components ofcomputer-readable program code being stored on more than one memory.

Additional Implementations

FIG. 23 illustrates a schematic flow diagram of a process 1000 ofauthenticating a user to perform a transaction in the payment processingsystem in accordance with some implementations. In some implementations,the payment processing system includes one or more payment modules 100(e.g., each associated with a respective payment accepting unit 120 suchan automatic retailing machine for dispensing goods and/or services),one or more mobile devices 150 (e.g., each executing the application 140for the payment processing system either as a foreground or backgroundprocess), and the server 130. The server 130 manages the paymentprocessing system and, in some cases, is associated with an entity thatsupplies, operates, and/or manufactures the one or more payment modules100. For brevity, the process 1000 will be described with respect to arespective payment module 100 and a respective mobile device 150 in thepayment processing system.

The payment module 100 broadcasts (1002), via a short-rangecommunication capability (e.g., BLE), a packet of information (sometimesalso herein called “advertised information”). The packet of informationat least includes an authorization code and an identifier associatedwith the payment module 100 (module ID). In some implementations, thepacket of information further includes a firmware version of the paymentmodule 100 and one or more status flags corresponding to one or morestates of the payment module 100 and/or the payment accepting unit 120.The information included in the packet broadcast by the payment module100 is further discussed below with reference to FIG. 24A.

In some implementations, the payment module 100 sends out a uniqueauthorization code every X seconds (e.g., 100 ms, 200 ms, 500 ms, etc.).In some implementations, the unique authorization codes are randomly orpseudo-randomly generated numbers. In some implementations, the paymentmodule 100 stores broadcasted authorization codes until a receivedauthorization grant token matches one of the stored authorization codes.In some implementations, the payment module 100 stores broadcastedauthorization codes for a predetermined amount of time (e.g., Y minutes)after which time an authorization code expires and is deleted. In someimplementations, the authorization code is encrypted with a sharedsecret key known by the server 130 but unique to the payment module 100.In some implementations, the payment module 100 initializes a randomnumber and then the authorization codes are sequential counts from thisrandom number. In such implementations, the payment module 100 storesthe earliest valid (unexpired) counter without a need to store everyvalid authorization code. In some implementations, the authenticationcode included in the broadcast packet of information is a hash value ofthe randomly or pseudo-randomly generated number or the sequentialnumber.

The mobile device 150 receives the broadcasted packet of information,and the mobile device 150 sends (1004), via a long-range communicationcapability (e.g., GSM, CDMA, Wi-Fi, or the like), an authorizationrequest to the server 130. For example, an application 140 that isassociated with the payment processing system is executing as aforeground or background process on the mobile device 150. In thisexample, the application 140 receives the broadcasted packet ofinformation when the mobile device 150 is within the communication zoneof the payment module 100 (i.e., BLE range) and either automaticallysends the authorization request to the server 130 or sends theauthorization request to the server 130 when the mobile device 150 iswithin the authorization zone of the payment module 100. In someimplementations, the broadcasted packet of information includes abaseline authorization zone threshold (i.e., an authorization zonecriterion) indicating a baseline RSSI that the mobile device 150 (or theapplication 140) is required to observe before being within theauthorization zone of the payment module 100. In some implementations,the mobile device 150 (or the application 140) offsets the baselineauthorization zone threshold based on the strength and/or reception ofthe short-range communication capability (e.g., BLE radio/transceiver)of the mobile device 150. In some implementations, the authorizationrequest at least includes the authorization code which was included inthe broadcasted packet of information, an identifier associated with theuser of the mobile device 150 or the user account under which the userof the mobile device 150 is logged into the application 140 (user ID),and the identifier associated with the payment module 100 (module ID).In some implementations, the authentication code included inauthorization request is the hash value in cleartext. The authorizationrequest is further discussed below with reference to FIG. 24B.

After receiving the authorization request, the server 130 processes(1006) the authorization request. In some implementations, the server130 decrypts the authorization code included in the authorizationrequest with the shared secret key corresponding to the payment module100. In some implementations, the server 130 determines whether the userassociated with the user ID in the authorization request has sufficientfunds in his/her account for the payment processing system to perform atransaction at the machine 120 that is associated with the paymentmodule 100 corresponding to the module ID in the authorization request.

The server 130 sends (1008), via a long-range communication capability(e.g., GSM, CDMA, Wi-Fi, or the like), an authorization grant token tothe mobile device 150. In some implementations, the server 130 does notsend the authorization grant token if the authorization code in theauthorization request cannot be decrypted with the shared secret keycorresponding to the payment module 100 (e.g., the authorization code iscorrupted or hacked). In some implementations, the server 130 does notsend the authorization grant token if the user associated with the userID in the authorization request does not have sufficient funds inhis/her account. In some implementations, in addition to theauthorization grant token, the server 130 sends a message directly tothe mobile device 150 which is not encrypted with the shared secret keycorresponding to the payment module 100. After receiving the message,the mobile device 150 displays an appropriate message to the user suchas insufficient balance or declined authorization. In someimplementations, the server 130 sends an authorization grant token foran amount equal to zero; in which case, the payment module 100interprets this as a declined or failed authorization which can resultfor any number of reasons including, but not limited to, insufficientbalance or credit.

The mobile device 150 receives the authorization grant token, and,subsequently, the mobile device 150 detects (1010) a trigger condition.In some implementations, the mobile device 150 (or the application 140)detects the trigger condition via the hand-free mode (e.g., uponentrance into the payment zone of the payment module 100) or manual mode(e.g., interacting with the user interface of the application 140 toinitiate a transaction with the payment accepting unit associated withthe payment module 100).

In some implementations, unused authorization grants (e.g., if there wasno trigger condition or it expired) are canceled by the mobile device150 by sending a cancellation message to the server 130 corresponding tothe unused authorization grant. In some implementations, the server 130denies or limits the number of authorization grants sent to the mobiledevice 150 until it has received transaction information or cancellationof authorization outstanding authorization grants sent to the mobiledevice 150.

In response to detecting the trigger condition, the mobile device 150sends (1012), via a short-range communication capability (e.g., BLE),the authorization grant token to the payment module 100. Subsequently,the machine 120 displays credit to the user (e.g., via one of thedisplays 122 or 124 shown in FIG. 19) and the user interacts with theinput mechanisms of the machine 120 (e.g., via the buttons 126 or atouch screen display 124 shown in FIG. 19) to purchase products and/orservices.

FIG. 24A illustrates a block diagram of a packet 1100 of informationbroadcast by the payment module 100 (e.g., in step 1002 of the process1000 in FIG. 23) in accordance with some implementations. In someimplementations, the packet 1100 at least includes: module ID 1102 andauthorization code 1104. In some implementations, the packet 110additional includes: a firmware version 1106 and one or more statusflags 1108.

In some implementations, the module ID 1102 is a unique identifiercorresponding to the payment module 100 (sometimes also herein calledthe “adapter module 100”) that broadcast the packet 1100.

In some implementations, the authorization code 1104 is a hash value incleartext. In some implementations, the payment module 100 randomly orpseudo-randomly generates a number or determines a sequential number(See step 1002 of process 1000 in FIG. 23) and performs a predeterminedhash function (e.g., SHA-256) on the number to produce the hash value asthe authorization code 1104. In some implementations, the authorizationcode 1104 is a unique code that is encrypted with a secret encryptionkey corresponding to the payment module 100. The secret encryption keyis shared with the server 130, which enables the server 130 to decryptthe authorization code 1104 and encrypt the authorization grant tokenbut not the mobile device 150. In some implementations, the encryptionbetween server 130 and payment module 100 is accomplished by two pairsof public/private keys.

In some implementations, the firmware version information 1106identifies a current firmware version 1112 of the payment module 100. Insome implementations, the firmware version information 1106 alsoincludes update status information 1114 indicating one or more packetsreceived by the payment module 100 to update the firmware or one or morepackets needed by the payment module 100 to update the firmware. SeeFIGS. 26A-26B and 30A-30D and the accompanying text for furtherdiscussion regarding updating the firmware of the payment module 100.

In some implementations, the one or more status flags 1108 indicate astate of the payment module 100 and/or the payment accepting unit 120associated with the payment module 100. In some implementations, the oneor more status flags 1108 indicate a state of the payment module 100such upload information indicator 1116 indicating that that the paymentmodule 100 has information to be uploaded to the server 130 (e.g.,transaction information for one or more interrupted transactions). Insome implementations, upload information indicator 1116 triggers themobile device 150 to connect to payment module 100 immediately (e.g., ifit has interrupted transaction information to be uploaded to the server130). See FIGS. 25A-25B and 29 and the accompanying text for furtherdiscussion regarding interrupted transactions. In some implementations,the one or more status flags 1108 indicate a state of the paymentaccepting unit 120 including one or more of an error indicator 1118(e.g., indicating that a bill and/or coin acceptor of the paymentaccepting unit 120 is experiencing a jam, error code, or malfunction), acurrency level indicator 1120 (e.g., indicating that the level of thebill and/or coin acceptor reservoir of the payment accepting unit 120 isfull or empty), and/or inventory level(s) indicator 1122 (e.g.,indicating that one or more products of the payment accepting unit 120.In some implementations, the one or more status flags 1108 are errorcodes issued by payment accepting unit 120 over the MDB.

In some implementations, the zone criteria information 1110 specifies anauthorization zone criterion 1124 (e.g., a baseline authorization zonethreshold indicating a baseline RSSI that the mobile device 150 (or theapplication 140) is required to observe before being within theauthorization zone of the payment module 100) and/or a payment zonecriterion 1126 (e.g., a baseline payment zone threshold indicating abaseline RSSI that the mobile device 150 (or the application 140) isrequired to observe before being within the payment zone of the paymentmodule 100). In some implementations, the baseline authorization zonethreshold and the baseline payment zone threshold are default valuesdetermined by the server 130 or stored as variables by the application140, in which case the authorization zone criterion 1124 and paymentzone criterion 1126 are offsets to compensate for the strength and/orreception of the short-range communication capability (e.g., BLEradio/transceiver) of the payment module 100. Alternatively, zonecriteria information 1110 includes a spread between the baselineauthorization zone threshold and the baseline payment zone threshold.Thus, the mobile device 150 (or the application 140) determines thebaseline authorization zone threshold and the baseline payment zonethreshold based on the spread value and a default value for either thebaseline authorization zone threshold or the baseline payment zonethreshold. For example, the spread indicates −10 db and the defaultbaseline payment zone threshold is −90 db; thus, the baselineauthorization zone threshold is −80 db. Continuing with this example,after determining the baseline authorization zone threshold and thebaseline payment zone threshold, the mobile device 150 (or theapplication 140) may further adjust the authorization zone thresholdand/or the payment zone threshold based on the strength and/or receptionof its short-range communication capability (i.e., BLEradio/transceiver).

FIG. 24B is a block diagram of an authorization request 1130 sent by themobile device 150 to the server 130 (e.g., in step 1004 of the process1000 in FIG. 23) in accordance with some implementations. In someimplementations, the authorization request 1130 at least includes: amodule ID 1102, a user ID 1134, and an authorization code 1104.

In some implementations, the module ID 1102 is a unique identifiercorresponding to the payment module 100 that broadcast the 1100 thatincluded the authorization code 1104.

In some implementations, the user ID 1134 is an identifier associatedwith the user of the mobile device 150 sending the authorization request1130 to the server 130. In some implementations, the user ID 1134 isassociated with the user account under which the user of the mobiledevice 150 is logged into the application 140.

In some implementations, the authorization code 1130 includes theauthorization code 1104 included in the packet 1100 of information thatwas broadcast by the payment module 100.

FIG. 24C is a block diagram of an authorization grant token 1140 sent bythe server 130 to the mobile device 150 (e.g., in step 1008 of theprocess 1000 in FIG. 23) in accordance with some implementations. Insome implementations, in accordance with a determination that theauthorization code 1136 included in the authorization request 1130 fromthe mobile device 150 is valid and that the user associated with themobile device 150 has sufficient funds in his/her account for thepayment processing system, the server 130 generates the authorizationgrant token 1140. In some implementations, the authorization grant token1140 at least includes: a module ID 1102, a user ID 1134, an authorizedamount 1146, (optionally) an expiration period offset 1148, and(optionally) the authorization code 1104.

In some implementations, the module ID 1102 is a unique identifiercorresponding to the payment module 100 that broadcast the packet 1100that included the authorization code 1104.

In some implementations, the user ID 1134 is an identifier associatedwith the user of the mobile device 150 that sent the authorizationrequest 1130 to the server 130.

In some implementations, the authorized amount 1146 indicates a maximumamount for which the user of the mobile device 150 is authorized for atransaction using the authorization grant token 1140. For example, theauthorized amount 1146 is predefined by the user of the mobile device150 or by the server 130 based on a daily limit or based on the user'stotal account balance or based on a risk profile of the user correspondto the user ID 1134.

In some implementations, the expiration period 1148 offset indicates anoffset to the amount of time that the payment module 100 holds theauthorization grant token 1140 valid for initiation of a transactionwith the machine 120 associated with the payment module 100. Forexample, the expiration period offset 1148 depends on the history andcredit of the user of mobile device 150 or a period predefined by theuser of mobile device 150.

In some implementations, the authorization grant token 1140 furtherincludes the authorization code 1104 that was included in theauthorization request 1130. In some implementations, when theauthorization code 1104 is the hash value, the server 130 encrypts theauthorization grant token 1140 including the hashed value with theshared secret encryption key associated with payment module 100.Subsequently, when mobile device 150 sends the authorization grant token1140 to payment module 100 after detecting a trigger condition, thepayment module 100 decrypts the authorization grant token 1140 using thesecret key known only to server 130 and payment module 100 (whichauthenticates the message and the authorization grant), and then matchesthe hash value included in the decrypted authorization grant token 1140to previously broadcast valid (unexpired) hash values (i.e., auth codes)to determine validity of the (which was known only by payment module100).

FIG. 24D illustrates a block diagram of transaction information 1150generated by the payment module 100 (e.g., in step 1204 of the process1200 in FIG. 25A) in accordance with some implementations. In someimplementations, the transaction information 1150 includes: atransaction ID 1152 for the respective transaction, a module ID 1154, auser ID 1156, (optionally) the authorization code 1158, transactionstatus information 1160, the transaction amount 1162, and otherinformation 1164.

In some implementations, the transaction ID 1152 is a unique identifiercorresponding to the respective transaction. In some implementations,the transaction ID 1152 is encoded based on or associated with the timeand/or date on which and the location at which the respectivetransaction took place.

In some implementations, the module ID 1154 is a unique identifiercorresponding to the payment module 100 that performed the respectivetransaction.

In some implementations, the user ID 1156 is an identifier associatedwith the user of the mobile device 150 that initiated the respectivetransaction.

In some implementations, the authorization code 1158 corresponds to theoriginal authorization code (e.g., auth code 1104, FIGS. 24 A-24C)and/or authorization grant token (e.g., auth grant token 1140, FIG. 24C)that was used to initiate the respective transaction. In someimplementations, the authorization code 1156 is encrypted with a uniqueencryption key corresponding to the payment module 100.

In some implementations, the transaction status information 1160includes an indication whether the respective transaction was completed,not-completed, or aborted. For example, the respective transaction isincomplete if a jam occurred at the payment accepting unit 120 and theuser did not receive the product associated with the respectivetransaction. For example, if the user walks away from the paymentaccepting unit 120 after money was credited for the respectivetransaction, the respective transaction is aborted. In another example,if respective transaction times out after a predetermined time periodbecause the user failed to select a product at the payment acceptingunit 120, the respective transaction is aborted. In another example, ifthe user actuates a bill or coin return mechanism of the paymentaccepting unit 120, the respective transaction is aborted.

In some implementations, the transaction amount 1162 indicates theamount of the respective transaction or the amount of each of multipletransactions (e.g., in a multi-vend scenario). In some implementations,the transaction amount 1162 is encrypted with a unique encryption keycorresponding to the payment module 100.

In some implementations, the other information 1164 includes otherinformation related to the respective transaction such as the itemsdispensed by the payment accepting unit 120 and the type of transaction(e.g., coins, bills, credit card, manual mode, hands-free mode, etc.).In some implementations, the other information 1164 includes otherinformation related to the payment module 100 and/or the paymentaccepting unit 120 associated with the payment module 100. For example,the other information 1164 includes a verification request to the server130 in order to implement new firmware. See FIGS. 26A-26B and theaccompanying text for further discussion of the verification request. Inanother example, the other information 1164 includes transactioninformation from one or more previous interrupted transactions. Inanother example, the other information 1164 includes transactioninformation for one or more transactions paid via bills and/or coins. Inanother example, the other information 1164 includes inventoryinformation as to one or more products of the payment accepting unit120.

FIG. 25 illustrates a schematic flow diagram of a process 1200 ofprocessing acknowledgement information in accordance with someimplementations. In some implementations, the payment processing systemincludes one or more payment modules 100 (e.g., each associated with arespective payment accepting unit 120 such an automatic retailingmachine for dispensing goods and/or services), one or more mobiledevices 150 (e.g., each executing the application 140 for the paymentprocessing system either as a foreground or background process), and theserver 130. The server 130 manages the payment processing system and, insome cases, supplies, operates, and/or manufactures the one or morepayment modules 100. For brevity, the process 1200 will be describedwith respect to a respective payment module 100 associated with arespective payment accepting unit 120 (machine 120) and a respectivemobile device 150 in the payment processing system. In the process 1200,the payment module 100 receives first acknowledgment information for afirst transaction via the mobile device 150 that initiated the firsttransaction.

The payment module 100 obtains (1202) a first notification indicatingcompletion of a first transaction from the machine 120. For example,after the process 1000 in FIG. 23, the user of the mobile device 150selects a product to purchase from the machine 120 by interacting withone or more input mechanisms of the machine 120 (e.g., buttons 126 or atouch screen display 124 shown in FIG. 19), and the machine 120dispenses the selected product. Continuing with this example, after theproduct is dispensed, the transaction is complete and the payment module100 obtains a notification from the machine of the completedtransaction. In some implementations, the notification includes theamount of the transaction and (optionally) machine status informationassociated with the machine 120 such as inventory information as to oneor more products of the payment accepting unit 120 and/or the like.

After obtaining the first notification, the payment module 100 generates(1204) first transaction information based on the first notification,and the payment module 100 stores the first transaction information. Insome implementations, the transaction information includes a transactionID for the first transaction, a module ID corresponding to paymentmodule 100, a user ID corresponding to the mobile device 150,transaction status information indicating that the first transaction iscomplete, and the transaction amount indicated by the firstnotification. In some implementations, the payment module 100 retainsthe authorization code included in the original broadcasted packetand/or the authorization grant token and includes the authorization codein the first transaction information. In some implementations, theauthorization code is encrypted with a secret key corresponding to thepayment module 100, which is shared with the server 130 but not themobile device 150. In some implementations, the first transactioninformation further includes other information such as the machinestatus information included in the first notification or transactioninformation corresponding to previous interrupted transaction(s). SeeFIG. 24D and the accompanying text for further discussion regardingtransaction information 1150.

The payment module 100 sends (1206), via a short-range communicationcapability (e.g., BLE), the first transaction information to the mobiledevice 150.

The mobile device 150 sends (1208), via a long-range communicationcapability (e.g., GSM, CDMA, Wi-Fi, or the like), the first transactioninformation to the server 130.

The server 130 processes (1210) the first transaction information. Forexample, the server 130 debits the account of the user associated withthe user ID in the first transaction information in the amount indicatedby the first transaction information.

The server 130 sends (1212), via a long-range communication capability(e.g., GSM, CDMA, Wi-Fi, or the like), first acknowledgment informationto the mobile device 150. In some implementations, the firstacknowledgment information acknowledges that the server 130 received thefirst transaction information. In some implementations, the firstacknowledgment information includes the user ID, the module ID, thetransaction ID, and (optionally) the authorization grant included in thetransaction information (e.g., auth grant 1158, FIG. 24D).

After receiving the first acknowledgement information, the mobile device150 sends (1214), via a short-range communication capability (e.g.,BLE), the first acknowledgment information to the payment module 100.

After receiving the first acknowledgment information, the payment module100 deletes (1216) the stored first transaction information.

Peripheral Expansion and Routing

FIG. 26 is a block diagram of an electronic device 1300 for retrofittinga machine 120 (also referred to herein as a payment accepting unit,vending machine, or retail machine) to accommodate a plurality ofelectronic peripheral devices 1330 (also referred to herein asperipherals) in accordance with some implementations. The device 1300 issimilar to and adapted from adapter module 100 (also referred to hereinas a payment module) as shown in FIG. 20 in that the device 1300connects to a multi-drop bus (MDB) of a machine 120 and, optionally,provides the payment processing functionalities discussed in FIGS. 7,8A-8G, 9A-9E, and 23 (e.g., via the internal peripheral 1340).

In some implementations, during normal operation, the machine 120includes a multi-drop bus (MDB) connecting a machine controller 1360(also referred to herein as a payment accepting unit controller) of themachine 120 with payment peripherals (e.g., other payment peripheral(s)1350, 1355 including coin acceptors, bill acceptors, cashless paymentdevices such as a payment card reader, and/or the like). In someimplementations, the device 1300 is connected in-line to the MDB asshown in FIGS. 17 and 18. In some implementations, the MDB protocol orthe machine 120 is configured to support a limited number of paymentperipherals or does not support particular payment peripherals. Forexample, in some circumstances, the machine 120 supports a maximum oftwo cashless payment devices, or the machine 120 only supports a billacceptor and a coin acceptor but not cashless payment devices or otherpayment peripherals. The device 1300 expands the number of paymentperipherals connected to the machine 120 beyond this limited number andenables support for a plurality of payment peripherals, which may or maynot be compliant with the machine 120 and/or the MDB protocol.

In FIG. 26, the device 1300 is configured (i) to perform as a virtualpayment peripheral of the machine controller 1360 of the machine 120 and(ii) to perform as a virtual machine controller (also referred to hereinas a master, or a virtual master) for the one or more paymentperipherals 1330. As such, in some implementations, the machinecontroller 1360 views the device 1300 as another payment peripheralconnected to the MDB, where the device 1300 sends signals to the machinecontroller 1360 in a manner as if originated by a peripheral 1330. Insome implementations, sending a signal to the machine controller 1360 ina manner as if originated by a peripheral 1330 includes labeling thesignal, or including a label with the signal, wherein the label includesthe peripheral device's registration information and/or identificationinformation (e.g., an address of the peripheral device). Stated anotherway, the device 1300 identifies itself to the machine controller 1360 asa peripheral 1330 by using the peripheral device's registration oridentification information. Moreover, in some implementations, the oneor more payment peripherals 1330 view the device 1300 as the machinecontroller 1360, where signals are sent to the one or more paymentperipherals 1330 in a manner as if originated by the machine controller1360. In some implementations, sending a signal to a peripheral 1330 ina manner as if originated by the machine controller 1360 includeslabeling the signal, or including a label with the signal, wherein thelabel includes the machine controller's identification information(e.g., an address of the machine controller). Stated another way, thedevice 1300 identifies itself to the peripheral device(s) 1330 as amachine controller 1360 by using the machine controller's identificationinformation. To accomplish this, the device 1300 (in its role as avirtual machine controller) manages and hosts the one or more paymentperipherals 1330. Additionally, the device 1300 translates addresses andmodifies the communications as necessary to ensure the machinecontroller 1360 understands the traffic that is coming through to it asa singular virtual payment peripheral.

In FIG. 26, the device 1300 includes a slave interface 1302 (e.g., themale adapter 720, FIG. 20) and an additional interface 1304 (e.g., thefemale adapter 730, FIG. 20) for connecting the device 1300 to the MDB.The device 1300 also includes a device controller 1310 with a processingunit 1312 (e.g., including one or more processors, cores,microcontrollers, microprocessors, or the like) and memory 1314 storingone or more programs for execution by the processing unit 1312. In someimplementations, the one or more programs cause the device 1300 toperform as a virtual payment peripheral of the machine controller 1360and to perform as a virtual machine controller for the one or morepayment peripherals 1330. In FIG. 26, the device 1300 also includes oneor more host interfaces 1320 (e.g., MDB ports or non-MDB ports) forconnecting the device 1300 with one or more payment peripherals 1330(e.g., payment peripherals 1330-A to 1330-N).

In some implementations, the machine 120 further includes one or moreother payment peripherals 1350, 1355 coupled with the MDB. Examplepayment peripherals of the one or more other payment peripherals includea bill acceptor, coin acceptor, or payment card reader. In theseimplementations, the device 1300 further includes an additionalinterface 1304 configured to couple the device with the one or moreother payment peripherals 1355 of the machine. For example, withreference to FIG. 26, the other payment peripheral(s) 1350 (e.g.,acceptors, coin acceptors, payment card readers, etc.) are connected tothe MDB before the device 1300 (e.g., prior to the slave interface 1302)and the other payment peripheral(s) 1355 (e.g., acceptors, coinacceptors, payment card readers, etc.) are connected to the MDB afterthe device 1300 (e.g., after the additional interface 1304).

In some implementations, the device 1300 further includes a pass-throughchannel configured to pass through signals from the one or more otherpayment peripherals 1355 to the machine controller 1360. For example,with reference to FIG. 26, the device 1300 includes a pass-throughchannel to enable signals from the machine controller 1360 to reach theother payment peripheral(s) 1355 and to enable signals from the otherpayment peripheral(s) 1355 to reach the machine controller 1360.

In some implementations, the device 1300 optionally includes an internalpayment peripheral 1340 with hardware, software, firmware, or acombination thereof for providing one or more of the payment processingfunctionalities described above with reference to FIGS. 7, 8A-8G, 9A-9E,and 23 (e.g., including the security unit 755 and the communicationsunit 770 shown in FIG. 20).

FIG. 27 illustrates a schematic flow diagram of a payment peripheralregistration process 1400 in accordance with some implementations. As aresult of process 1400, the device 1300 is registered as a slave (e.g.,as a payment peripheral) to the machine controller 1360, and the paymentperipheral(s) 1330 are registered as slaves to the device 1300, forexample, in accordance with MDB protocol. Stated another way, the device1300 acts (i) as a slave to the machine controller 1360 (e.g., withrespect to operations 1402-1408), and (ii) as a master (machinecontroller) to the payment peripheral(s) 1330 (e.g., with respect tooperations 1412-1428).

In some implementations, the machine controller 1360 (FIG. 26) polls(1402) the device 1300. For example, the machine controller 1360 sends apoll command to the device 1300.

In some implementations, in response to the poll command, the device1300 sends (1404) a reset signal to the machine controller 1360. Forexample, the device 1300 sends the reset signal to the machinecontroller 1360 if the device 1300 has not yet been registered as aslave (e.g., a payment peripheral). In another example, the device 1300sends the reset signal to re-register itself as a slave. In someimplementations, the device 1300 identifies itself as a coin acceptor, abill acceptor, or a cashless payment device to the machine controller1360 via the reset signal.

In some implementations, in response to the reset signal, the machinecontroller 1360 sends (1406) a setup signal to the device 1300. In someimplementations, the setup signal includes an address assigned to thedevice 1300.

In some implementations, after receiving and processing the setupsignal, the device 1300 sends (1408) an acknowledgement to the machinecontroller 1360 confirming registration as a slave.

Upon sending the acknowledgement, the device 1300 has been registered asa slave (e.g., a payment peripheral) to the machine controller 1360.

In some implementations, the device 1300 polls (1412) the paymentperipheral 1330-A.

In some implementations, in response to the poll command, the paymentperipheral 1330-A sends (1414) a reset signal to the device 1300. Forexample, the payment peripheral 1330-A sends the reset signal to thedevice 1300 if it has not yet been registered as a slave (e.g., apayment peripheral) to the device 1300. In another example, the paymentperipheral 1330-A sends the reset signal to re-register itself as aslave. In some implementations, the payment peripheral 1330-A identifiesitself as a coin acceptor, a bill acceptor, or a cashless payment deviceto the device 1300 via the reset signal.

In some implementations, in response to the reset signal, the device1300 sends (1416) a setup signal to the payment peripheral 1330-A. Insome implementations, the setup signal includes an address assigned tothe payment peripheral 1330-A.

In some implementations, after receiving and processing the setupsignal, the payment peripheral 1330-A sends (1418) an acknowledgement todevice 1300 confirming registration as a slave.

In some implementations, the device 1300 polls (1422) the paymentperipheral 1330-N.

In some implementations, in response to the poll command, the paymentperipheral 1330-N sends (1424) a reset signal to the device 1300. Forexample, the payment peripheral 1330-N sends the reset signal to thedevice 1300 if it has not yet been registered as a slave (e.g., apayment peripheral). In another example, the payment peripheral 1330-Nsends the reset signal to re-register itself as a slave. In someimplementations, the payment peripheral 1330-N identifies itself as acoin acceptor, a bill acceptor, or a cashless payment device to thedevice 1300 via the reset signal.

In some implementations, in response to the reset signal, the device1300 sends (1426) a setup signal to the payment peripheral 1330-N. Insome implementations, the setup signal includes an address assigned tothe payment peripheral 1330-N.

In some implementations, after receiving and processing the setupsignal, the payment peripheral 1330-N sends (1428) an acknowledgement tothe device 1300 confirming registration as a slave.

FIGS. 28A-28B illustrate a schematic flow diagram of a payment process1500 in accordance with some implementations. In some implementations,(i) the device 1300 has already been registered as a slave (e.g., apayment peripheral) to the machine controller 1360, and (ii) the paymentperipherals 1330-A, 1330-N have already been registered as slaves (e.g.,as payment peripherals) to the device 1300 according to process 1400(FIG. 27). Stated another way, the device 1300 acts (i) as a slave tothe machine controller 1360 (e.g., with respect to operations 1502-1504,1520-1528, 1540-1548, and 1554-1556), and (ii) as a master (machinecontroller) to the payment peripheral(s) 1330 (e.g., with respect tooperations 1506-1518, 1530-1538, 1550-1552, and 1558-1564).

In some implementations, the machine controller 1360 polls the device1300, along with other payment peripherals connected to the MDB andregistered as slaves (e.g., other payment peripherals 1350, 1355 (FIG.26)), according to a predetermined time period (e.g., 5 ms). Forexample, the predetermined time period is assigned by the MDB protocolor specification (e.g., versions 1.0 to 3.0 or higher), which isincorporated herein by reference in its entirety. In response to thepoll commands, all slave devices (e.g., at least including the device1300) respond with an acknowledgment (e.g., indicating that it is stillpresent on the MDB) or with another signal (e.g., indicating anotherstate). In some implementations, in response to a command from themachine controller 1360, the device 1300 immediately responds to thecommand and asynchronously relays the command to at least one of thepayment peripheral(s) 1330.

In some implementations, in a manner similar to the machine controller1360, the device 1300 also polls the payment peripheral(s) 1330according to the predetermined time period (e.g., 5 ms). For example,the device 1300 polls the payment peripheral(s) 1330 whenever the device1300 is polled by the machine controller 1360.

In some implementations, the machine controller 1360 polls (1502) thedevice 1300.

In response to the polling command in operation 1502, the device 1300sends (1504) an acknowledgment to the machine controller 1360.

In response to or independent of the polling command in operation 1502,the device 1300 polls (1506) the payment peripheral 1330-N. In responseto the polling command in operation 1506, the payment peripheral 1330-Nsends (1508) an acknowledgment to the device 1300.

In response to or independent of the polling command in operation 1502,the device 1300 polls (1510) the payment peripheral 1330-A. In responseto the polling command in operation 1510, the payment peripheral 1330-Asends (1512) a request to begin a payment session. For example, therequest to begin the payment session is sent in response to a userinserting payment (e.g., a bill(s) or coin(s)) into the paymentperipheral 1330-A prior to the polling command in operation 1510.

In response to the request to begin the payment session, the device 1300sends (1514) an acknowledgment to the payment peripheral 1330-A.

In response to the request to begin the payment session, the device 1300also sends (1516) a disable command to the payment peripheral 1330-N soas to disable the payment peripheral 1330-N while processing the paymentsession for the payment peripheral 1330-A. In response to the disablecommand, the payment peripheral 1330-N sends (1518) an acknowledgment tothe device 1300.

The machine controller 1360 polls (1520) the device 1300.

In response to the polling command in operation 1520, the device 1300sends (1522) a request to begin a payment session to the machinecontroller 1360. For example, the request to begin the payment session(sent to the machine controller 1360 in operation 1522) mirrors therequest to begin the payment session (received from the paymentperipheral 1330-A in operation 1512).

In response to the request to begin the payment session in operation1522, the machine controller 1360 sends (1524) an acknowledgement to thedevice 1300 and also sends (1526) a vend request to the device 1300. Inprocess 1500, vending of a service or product is taken as a non-limitingexample.

In response to receiving the vend request, the device 1300 sends (1527)an acknowledgment to the machine controller 1360.

In some implementations, the machine controller 1360 polls (1528) thedevice 1300 N times prior to the device 1300 sending a vend approvedsignal in operation 1540. In some implementations, the device 1300responds to the N polling commands with acknowledgments indicating thatthe device 1300 is still present and processing the vend request.

In response to receiving the vend request in operation 1526, the device1300 relays (1530) the vend request to the payment peripheral 1330-A.

In response to the vend request in operation 1530, the paymentperipheral 1330-A sends (1532) an acknowledgement to the device 1300.

Subsequently, the device 1300 polls (1534) the payment peripheral1330-A. In response to the polling command in operation 1534, thepayment peripheral 1330-A sends (1536) a vend approved signal to thedevice 1300. For example, the vend approved signal indicates that thepayment inserted by the user was not refunded and was used to purchase aservice or product.

In response to receiving the vend approved signal in operation 1536, thedevice 1300 sends (1538) an acknowledgment to the payment peripheral1330-A and also relays (1540) the vend approved signal to the machinecontroller 1360.

In response to receiving the vend approved signal in operation 1540, themachine controller 1360 sends (1542) an acknowledgment to the device1300 and also sends (1544) a request to the device 1300 to indicatewhether the vend was a success or a failure.

In response to receiving the request in operation 1544, the device 1300sends (1546) a response to the machine controller 1360 indicating thatthe vend was a success or a failure and also relays (1550) the requestto the payment peripheral 1330-A to indicate whether the vend was asuccess or a failure.

In response to the request in operation 1550, the payment peripheral1330-A sends (1552) an acknowledgement to the device 1300.

In response to receiving the response in operation 1546, the machinecontroller 1360 sends (1548) an acknowledgement to the device 1300 andalso sends (1554) a command to end the payment session to the device1300.

In response to receiving the command to end the payment session inoperation 1554, the device 1300 sends (1556) an acknowledgment to themachine controller 1360 and relays (1558) the command to end the paymentsession to the payment peripheral 1330-A.

In response to the command to end the payment session in operation 1558,the payment peripheral 1330-A sends (1560) an acknowledgment to thedevice 1300.

After receiving the acknowledgment from the payment peripheral 1330-A inoperation 1560, the device 1300 sends (1562) an enable command to thepayment peripheral 1330-N so as to enable the payment peripheral 1330-Nafter completion of the payment session for the payment peripheral1330-A. In response to the enable command received in operation 1562,the payment peripheral 1330-N sends (1564) an acknowledgment to thedevice 1300.

FIG. 29 illustrates a flowchart diagram of a method 1600 of retrofittinga machine controller 1360 (also referred to herein as a paymentaccepting unit; vending machine; retail machine; and/or a processor orcontroller of a payment accepting unit, vending machine, or retailmachine) to accommodate a plurality of payment peripherals 1330 (alsoreferred to herein as electronic peripheral devices, peripheral devices,or peripherals) in accordance with some implementations. In someimplementations, the method 1600 is performed at a device controller1310 of an electronic device 1300 with one or more processing units 1312(processors), memory 1314, a slave interface 1302 configured to couplethe device 1300 with the machine controller 1360 via a multi-drop bus(MDB), and one or more host interfaces 1320 configured to couple thedevice 1300 with one or more payment peripherals 1330 (e.g., a coinacceptor, a bill acceptor, a cashless payment device such as a paymentcard reader, and the like), where a respective payment peripheral 1330is decoupled from an MDB interface of the machine controller 1360 andcoupled with a respective host interface 1320, and where the paymentperipheral(s) 1330 are configured to communicate via MDB protocol. Forexample, in some implementations, the method 1600 is performed by thedevice 1300 or a component thereof (e.g., device controller 1310). Insome implementations, the method 1600 is governed by instructions thatare stored in a non-transitory computer readable storage medium (e.g.,memory 1314) and the instructions are executed by one or more processors(e.g., processing unit(s) 1312) of the device. Optional operations areindicated by dashed lines (e.g., boxes with dashed-line borders).

The device 1300 performs (1602) as a virtual payment peripheral (slave)for the machine controller 1360 by registering itself as a slave to themachine controller 1360, and the device 1300 performs as a virtualmachine controller (master) for the one or more payment peripherals 1330by registering the one or more payment peripherals 1330 as slaves to thedevice 1300 using the MDB protocol. In some implementations, the MDBprotocol supports a limited number of payment peripherals 1330. Thedevice 1300 expands the number of payment peripherals 1330 that can beconnected to the machine controller 1360 beyond this limited number by(i) emulating the machine controller 1360 to the payment peripheral(s)1330 coupled with the host interface(s) 1320 and (ii) emulating apayment peripheral 1330 to the machine controller 1360. As such, in someimplementations, the machine controller 1360 views the device 1300 asanother payment peripheral 1330 connected to the MDB, where the device1300 sends signals to the machine controller 1360 in a manner as iforiginated by the device 1300 that is functioning as a singular virtualpayment peripheral 1330 (in other words, in a manner as if originated bya payment peripheral 1330). Moreover, in some implementations, thepayment peripheral(s) 1330 view the device 1300 as the machinecontroller 1360, where the device 1300 sends signals to the paymentperipheral(s) 1330 in a manner as if originated by the machinecontroller 1360.

In some implementations, registering the device 1300 as a slave to themachine controller 1360 further comprises (1602 a): identifying thedevice 1300 to the machine controller 1360 as a cashless paymentperipheral; and accepting registration of the device 1300 with themachine controller 1360 as a cashless payment peripheral. For example,the device 1300 identifies itself to the machine controller 1360 as acashless payment device (e.g., a payment card reader) when sending thereset signal to the machine controller 1360 in operation 1404, and thedevice 1300 accepts registration as a cashless payment device whenreceiving the setup signal from the machine controller 1360 in operation1406 (see FIG. 27).

In some implementations, registering the device 1300 as a slave to themachine controller 1360 further comprises (1602 b): identifying thedevice 1300 to the machine controller 1360 as a coin acceptorperipheral; and accepting registration of the device 1300 with themachine controller 1360 as a coin acceptor peripheral. For example, thedevice 1300 identifies itself to the machine controller 1360 as a coinacceptor when sending the reset signal to the machine controller 1360 inoperation 1404, and the device 1300 accepts registration as a coinacceptor when receiving the setup signal from the machine controller1360 in operation 1406 (see FIG. 27).

In some implementations, registering the device 1300 as a slave to themachine controller 1360 further comprises (1602 c): identifying thedevice 1300 to the machine controller 1360 as a bill acceptorperipheral; and accepting registration of the device 1300 with themachine controller 1360 as a bill acceptor peripheral. For example, thedevice 1300 identifies itself to the machine controller 1360 as a billacceptor/validator when sending the reset signal to the machinecontroller 1360 in operation 1404, and the device 1300 acceptsregistration as a bill acceptor/validator when receiving the setupsignal from the machine controller 1360 in operation 1406 (see FIG. 27).

The device 1300 receives (1604) a command (in the form of a signal) fromthe machine controller 1360 via the slave interface 1302, where signalsfrom the machine controller 1360 are sent in a manner as if sent to asingular payment peripheral 1330. For example, with reference to process1500, the machine controller 1360 sends a command to the device 1300 toend the payment session in operation 1554 (see FIG. 28B).

In response to receiving the command from the machine controller 1360,the device 1300 sends (1604) an acknowledgement to the command to themachine controller 1360 via the slave interface 1302, where signals aresent to the machine controller 1360 in a manner as if originated by thedevice 1300 that is functioning as a singular virtual payment peripheral1330 (in other words, as if originated by a payment peripheral 1330);and relays the command to the respective payment peripheral 1330 via therespective host interface 1320 corresponding to the respective paymentperipheral 1330, where the device 1300 sends signals to and receivessignals from the machine controller 1360 asynchronous of the device 1300sending signals to and receiving signals from the one or more paymentperipherals 1330 (in other words, communications between the device 1300and the machine controller 1360 are not necessarily synchronized tocommunications between the device 1300 and the payment peripheral(s)1330). Continuing with the example above, with reference to process1500, in response to receiving the command to end the payment session inoperation 1554, the device 1300 sends an acknowledgment to the machinecontroller 1360 in operation 1556 in a manner as if originated by thedevice that is functioning as a singular virtual payment peripheral 1330(in other words, in a manner as if originated by the payment peripheral1330). Continuing with this example, in response to receiving thecommand to end the payment session in operation 1554, the device 1300also asynchronously relays the command to end the payment session to thepayment peripheral 1330-A in operation 1558. As such, the command isrelayed to the payment peripheral 1330-A asynchronous of sending theacknowledgment to the machine controller 1360 (in other words, thesignals 1556 and 1558 are not necessarily synchronized).

In some implementations, in response to relaying the command, the device1300 receives (1608) via the respective host interface 1320corresponding to the respective payment peripheral 1330 a response fromthe respective payment peripheral 1330. Continuing with the exampleabove, with reference to process 1500, in response to the relayedcomplete session command in operation 1558, the payment peripheral1330-A sends an acknowledgment to the device 1300 in operation 1560.

In some implementations, in response to receiving the response from therespective payment peripheral 1330, the device 1300: sends anacknowledgement to the respective payment peripheral 1330, where signalsare sent to the one or more payment peripherals 1330 in a manner as iforiginated by the machine controller 1360; and relays the response tothe machine controller 1360 via the slave interface 1302, where thedevice 1300 sends signals to and receives signals from the machinecontroller 1360 asynchronous of the device sending signals to andreceiving signals from the one or more payment peripherals 1330 (inother words, communications between the device 1300 and the machinecontroller 1360 are not necessarily synchronized to communicationsbetween the device 1300 and the payment peripheral(s) 1330). In someimplementations, in response to receiving the response from therespective payment peripheral 1330, the device forgoes the above steps(e.g., the device 1300 does not relay the acknowledgement 1560 to themachine controller 1360 because the device 1300 had already acknowledgedthe machine controller 1360's session complete command in operation1556).

In some implementations, the device 1300 receives (1610) a command froma respective payment peripheral 1330 via the respective host interface1320 corresponding to the respective payment peripheral 1330, wheresignals from the payment peripheral(s) 1330 are sent to the device 1300in a manner as if sent to the machine controller 1360, and, in responseto receiving the command from the respective payment peripheral 1330,the device 1300 sends (1612) an acknowledgement to the command to therespective payment peripheral 1330, where signals are sent from thedevice 1300 to the payment peripheral(s) 1330 in a manner as iforiginated by the machine controller 1360; and relays the command to themachine controller 1360 via the slave interface 1302, where the device1300 sends signals to and receives signals from the machine controller1360 asynchronous of the device 1300 sending signals to and receivingsignals from the payment peripheral(s) 1330 (in other words,communications between the device 1300 and the machine controller 1360are not necessarily synchronized to communications between the device1300 and the payment peripheral(s) 1330). For example, with reference toprocess 1500, when polled in operation 1534, the payment peripheral1330-A sends a vend approved signal to the device 1300 in a manner as ifsent to the machine controller 1360 in operation 1536. Continuing withthis example, in response to receiving the vend approved signal inoperation 1536, the device 1300 sends an acknowledgement to the paymentperipheral 1330-A in a manner as if originated by the machine controller1360 in operation 1538. Continuing with this example, in response toreceiving the vend approved signal in operation 1536, the device 1300also asynchronously relays the vend approved signal to the machinecontroller 1360 in operation 1540. As such, the command is relayed tothe machine controller 1360 asynchronous of sending the acknowledgmentto the payment peripheral 1330-A (in other words, the signals 1538 and1540 are not necessarily synchronized).

In some implementations, in response to relaying the command, the device1300 receives (1614) via the slave interface 1302 a response from themachine controller 1360. Continuing with the example above, withreference to process 1500, in response to the relayed vend approvedsignal in operation 1540, the machine controller 1360 sends anacknowledgment to the device 1300 in operation 1542.

In some implementations, the device 1300 further includes an internalpayment peripheral 1340 including a short-range communication capabilitycorresponding to a short-range communication protocol, where theshort-range communication capability is configured to communicate withone or more mobile devices, and where each of the one or more mobiledevices is configured with (i) a complimentary short-range communicationcapability and (ii) a long-range communication capability correspondingto a long-range communication protocol. For example, with reference toFIG. 26, the device 1300 includes the internal payment peripheral 1340which includes hardware, software, firmware, or a combination thereoffor providing the payment processing functionalities discussed in FIGS.7, 8A-8G, 9A-9E, and 23 (e.g., the security unit 755 and thecommunications unit 770 as shown in FIG. 20). For example, therespective mobile device corresponds to mobile device 150 (FIG. 21) withlong-range communication capability 872 and short-range communicationcapability 876.

In some implementations, the device 1300 receives (1616) a transactionrequest via the short-range communication capability from a respectivemobile device to perform a transaction with the machine controller 1360,the device 1300 validates the transaction request, where validation ofthe transaction request indicates that the respective mobile device isauthorized to initiate payment for the transaction by a remote servervia the respective mobile device's long-range communication capability,and, in accordance with a determination that the transaction request isvalid, the device 1300 causes the machine controller 1360 to perform therequested transaction by, for example, issuing a signal to perform thetransaction to the machine controller 1360 via the slave interface 1302.In some implementations, the device 1300 or a component thereof (e.g.,internal payment peripheral 1340, FIG. 26) receives a transactionrequest via the short-range communication capability (e.g., BLE, NFC, orthe like) from the respective mobile device 150 (FIGS. 7, 8A-8G, 9A-9E,and 21), and the device 1300 or a component thereof (e.g., internalpayment peripheral 1340, FIG. 26; or the device controller 1310, FIG.26) validates the transaction request from the respective mobile device150 by determining whether an AuthGrant or authorization grant tokenassociated with the transaction request includes a valid authorizationcode. In some implementations, in accordance with a determination thatthe transaction request is associated with a valid authorization code,the device 1300 or a component thereof (e.g., internal paymentperipheral 1340, FIG. 26; or the device controller 1310, FIG. 26) issuesa command to the machine controller 1360 to perform the requestedtransaction via the slave interface 1302 in a manner as if originated bythe device 1300 that is functioning as a singular virtual paymentperipheral 1330 or 1340 (in other words, in a manner as if originated bya payment peripheral 1330 or 1340).

In some implementations, in accordance with a determination that acommand received from the respective payment peripheral 1330 correspondsto a transaction, the device 1300 stores (1618) transaction informationat least including an amount of the transaction associated with anidentifier for the respective payment peripheral 1330; after storing thetransaction information, the device 1300 sends the transactioninformation to the respective mobile device via the short-rangecommunication capability; and issues a command to the respective mobiledevice to send the transaction information to the remote server via therespective mobile device's long-range communication capability.

In some implementations, the device 1300 or a component thereof (e.g.,the internal payment peripheral 1340, FIG. 26; or the device controller1310, FIG. 26) monitors commands and signals from the one or morepayment peripherals 1330 that are relayed to the machine controller 1360and, in accordance with a determination that a command or signal isassociated with a transaction, stores transaction information such asthe transaction amount and the respective payment peripheral 1330associated with the transaction. For example, the device 1300 storestransaction information for each of the one or more payment peripherals1330 in a table that associates the transaction information with apayment peripheral type (e.g., bill acceptor, coin acceptor, paymentcard reader, etc.). In some implementations, the device 1300 or acomponent thereof (e.g., the internal payment peripheral 1340, FIG. 26;or the device controller 1310, FIG. 26) sends the table of transactioninformation or a portion thereof to the respective mobile device 150that sent the transaction request (or another mobile device 150 thatperforms a transaction with the device 1300) via the short-rangecommunication capability. In some implementations, the device 1300 or acomponent thereof (e.g., the internal payment peripheral 1340, FIG. 26;or the device controller 1310, FIG. 26) commands the respective mobiledevice 150 to send the table of transaction information or the portionthereof to the server 130 via the mobile device's long-rangecommunication capability. As such, the device 1300 uses the respectivemobile device 150 as a communication bridge to the server 130.

In some implementations, the device 1300 or a component thereof (e.g.,the internal payment peripheral 1340, FIG. 26; or the device controller1310, FIG. 26) also monitors the commands and signals from the one ormore payment peripherals 1330 that are relayed to the machine controller1360 and, in accordance with a determination that a command or signal isassociated with an error code (e.g., a coin jam, low coin or bill count,etc.) or other information associated with the operation of the one ormore payment peripherals 1330, stores corresponding operationinformation. In some implementations, the device 1300 also sends theoperation information along with the table of transaction information orthe portion thereof to the server 130 using the respective mobile device150 as a communication bridge to the server 130.

The particular order in which the operations in FIG. 29 have beendescribed is merely exemplary and is not intended to indicate the onlyorder in which the operations could be performed. One of ordinary skillin the art would recognize various ways to reorder the operationsdescribed herein. Additionally, details of other processes describedherein with respect to other methods described herein are alsoapplicable in an analogous manner to the method 1600 described abovewith respect to FIG. 29.

Providing External Access to Peripherals

In some implementations, the electronic device 1300 receives, from amobile device 150 via the short-range communication capability of theinternal peripheral 1340, a request to access one or more of theperipherals 1330. In response to this request, the device 1300intercepts signals received from peripheral(s) 1330 via respective hostinterface(s) 1320 (e.g., a payment signal reporting an amount of moneyreceived at a bill acceptor peripheral or a coin acceptor peripheral).Instead of relaying the signals to the machine controller 1360, thedevice 1300 relays the signals (or data based on the signals) to themobile device 150 through the internal peripheral 1340. While the device1300 is intercepting signals received from the peripheral(s) 1330 (i.e.,relaying the signals to the internal peripheral 1340 instead of themachine controller 1360), the device 1300 responds to commands that areaddressed to the peripheral(s) 1330 (e.g., poll commands sent from themachine controller 1360) with acknowledgements (e.g., merely reportingpresence), rather than relaying the commands to the peripheral(s) 1330.

By intercepting signals as described herein, the device 1300 can provideexternal access to the peripheral(s) 1330 (also referred to as providingperipheral access to an external device). More specifically, the device1300 may be configured to enable an external device (e.g., a mobiledevice 150, or any device that is physically external to the machine 120and in communication with the device 1300) to access functionalityprovided by the peripheral(s) 1330 of the machine 120. As used herein,the term “access” may refer to provision of data based on functionalityof a peripheral 1330, but does not require direct communication betweenthe external device and the peripheral 1330 being accessed. By providingan external device with access to a peripheral 1330, the external deviceis provided with the benefit of functionality of the peripheral 1330.For example, if the peripheral 1330 is a bill collector, an externaldevice with access to functionality of the bill collector may beprovided with data indicating a state of the bill collector or any otherdata associated with functionality of the bill collector (e.g., anindication that the bill collector has just received a $1 bill).

In one example scenario, an application executing on a mobile device 150in communication with the device 1300 may be provided access to a billaccepter peripheral 1330 of a machine 120, thereby providing a way forthe application to accept cash payments. As such, capabilities of themobile device 150 (and, therefore, applications executing on the mobiledevice 150) are augmented when given access to functionality provided bythe peripheral(s) 1330 of a machine 120 as described herein. Such anapplication executing on a mobile device 150 (referred to herein as amobile application) may be configured to sell products and/or servicesthat are not necessarily stocked by the machine 120 of the peripheral1330 being accessed, but benefit from the availability of the option topay for the product and/or service with cash. For example, anapplication executing on a mobile device 150 may sell lottery tickets,which, according to the laws of some jurisdictions, can only bepurchased using cash. Example products may include physical productsthat are available at a location associated with the machine 120 (e.g.,provided by a store attendant or bank teller), or may include virtualproducts that are not required to be picked up or otherwise physicallydelivered (e.g., lottery tickets associated with virtual lotteryapplications that do not require delivery or use of a physical scratchcard). Example services include banking (e.g., using a bill acceptorperipheral 1330 of a machine 120 to deposit cash to an account of a bankor credit union, regardless of whether the bank or credit union has aphysical location), or any other service requiring or otherwiseproviding the option to deposit cash to an account (e.g., a gamingservice with add-on functionality purchasable with cash, a peer-to-peermoney transfer service enabling a sender to deposit cash into the billacceptor of a machine 120 and a receiver to withdraw cash by accessingthe cash return module of another machine 120, or any other serviceaccepting cash payments). Such products and/or services may be relatedto products and/or services vended or advertised by the machine 120, orthey may be independent of products and/or services vended or advertisedby the machine 120 (e.g., functionality of the bill acceptor of a sodamachine may be accessed by a mobile application selling lottery tickets,or functionality of the coin acceptor of a laundry machine may beaccessed by a mobile gaming application configured to accept payments inreturn for in-game add-on features).

FIG. 30A-30B illustrate block diagrams of normal operations 3002 andintercept operations 3004 of a device 1300 for retrofitting a machine120 to provide external access to an electronic peripheral 1330 inaccordance with some implementations. The device 1300 and relatedcomponents (1302-1360) correspond to similarly numbered features asdescribed above with reference to FIG. 26, and some are not furtherdiscussed for purposes of brevity. Further, while some features depictedin FIG. 26 are not depicted in FIGS. 30A-30B (for purposes of clarity),each of the concepts described above with regard to FIGS. 26-29 equallyapply to the implementations recited herein with regard to FIGS.30A-30B, 31-34, and 35A-35B.

In FIG. 30A, the device 1300 is configured to relay signals between themachine controller 1360 and the peripheral 1330. For example, the device1300 receives a payment received signal (3118) from the peripheral 1330(e.g., upon receiving a $1 bill) and relays the signal (3124) to themachine controller 1360. Regarding polling in normal operations, thedevice 1300 is configured to respond to polls received from the machinecontroller 1360 and asynchronously send polls to the peripheral 1330. Asdescribed above with reference to FIGS. 28A-28B, the device 1300responds to polls received from the machine controller 1360 based onpoll responses received from the peripheral 1330. As such, whileperforming normal operations, the device 1300 acts as a signal routerbridging the peripheral 1330 and the machine controller 1360 asdescribed above with reference to FIGS. 28A-28B and as described in moredetail below with reference to FIGS. 31-32.

In FIG. 30B, the device 1300 is configured to acknowledge signalsreceived from the machine controller 1360 (e.g., acknowledge polls), butnot relay those signals (or otherwise send any signals based on thosereceived signals) to the peripheral 1330. Further, instead of relayingsignals received from the peripheral 1330 (e.g., a payment receivedsignal 3306) to the machine controller 1360, the device 1300 insteadrelays signals received from the peripheral 1330 (or sends signals basedon the received signals, such as a transmit transaction signal 3312) toan external device (e.g., a mobile device 150) via the internalperipheral 1340. For example, the device 1300 receives a paymentreceived signal 3306 from the peripheral 1330 (e.g., upon receiving a $1bill), and relays the payment received signal 3306, or a signal based onthe payment received signal (e.g., a transmit transaction signal 3312),to a mobile device 150 via the internal peripheral 1340. This disclosurerefers to the operation of relaying a signal received from theperipheral 1330 to an external device, instead of to the machinecontroller 1360, as intercepting the signal, or as an interceptoperation. While performing intercept operations, the device 1300 actsas a signal router bridging the peripheral 1330 and an external device(e.g., a mobile device 150) as described in more detail below withreference to FIG. 33-34.

In some implementations, signals received at the device controller 1310include at least (i) a destination address, and (ii) message data. Morespecifically, signals received at the device 1300 from a peripheral 1330include the address of a specified master (referred to herein as amaster address), and signals received at the device 1300 from themachine controller 1360 include the address of a specified peripheral1330 (referred to herein as a peripheral address). The master andperipheral addresses may be identified or otherwise assigned during aregistration process (e.g., during setup operations 1406, 1416, and 1426in FIG. 27, setup operations 3102 and 3106 in FIG. 31, setup operation3208 in FIG. 32, and setup operation 3416 in FIG. 34). The message datamay include a representation of the state of the originating module(e.g., a signal received from a particular peripheral 1330 may include arepresentation of a state of the particular peripheral 1330), or anyother data related to a function of the originating module. As usedherein, the term “originating module” refers to the module (e.g.,peripheral 1330 or machine controller 1360) that sent the signalincluding the destination address or message data being described.

For example, when a signal sent by the peripheral 1330 to the device1300 specifies the address of the machine controller 1360 as the masteraddress, the device controller 1310 relays the signal, including thesignal's message (e.g., indicating receipt of a $1 bill) to the machinecontroller 1360 as depicted in FIG. 30A. On the other hand, when asignal sent by the peripheral 1330 to the device 1300 specifies theaddress of the device 1300 as the master address, the device controller1310 relays the signal, including the signal's message (e.g., indicatingreceipt of a $1 bill), or processes the signal and sends a signal with amessage based at least in part on the originally received message (e.g.,indicating a $1 bill was received and not refunded within a thresholdamount of time) to an external device (e.g., a mobile device 150) asdepicted in FIG. 30B.

FIGS. 31-34 illustrate schematic flow diagrams of a process forproviding external access to an electronic peripheral 1330 of a machine120 in accordance with some implementations. FIG. 31 depicts a method3100 of normal operations (e.g., 3002 in FIG. 30A), FIG. 32 depicts amethod 3200 of a transition from normal operations to interceptoperations (e.g., 3004 in FIG. 30B), FIG. 33 depicts a method 3300 ofintercept operations, and FIG. 34 depicts a method 3400 of a transitionfrom intercept operations to normal operations.

The operations in FIGS. 31-34 are governed by instructions that arestored in a computer memory or non-transitory computer readable storagemedium of any combination of a machine controller 1360, an electronicdevice 1300 (e.g., memory 1314 in FIG. 26), an electronic peripheral1330, a mobile device 150, and a server 130. The instructions areexecuted by one or more processors of any combination of the machinecontroller 1360, the electronic device 1300 (e.g., processing unit 1312in FIG. 26), the electronic peripheral 1330, the mobile device 150, andthe server 130. Each computer readable storage medium may include amagnetic or optical disk storage device, solid state storage devicessuch as Flash memory, or other non-volatile memory device or devices.The instructions stored on each computer readable storage medium mayinclude one or more of: source code, assembly language code, objectcode, or other instruction format that is interpreted by one or moreprocessors. Some operations in FIGS. 31-34 may be combined and/or theorder of some operations in FIGS. 31-34 may be changed.

While the methods 3100-3400 depict an implementation including oneperipheral 1330 (for purposes of brevity and clarity of the conceptsdescribed herein), the concepts described herein also apply toimplementations including a plurality of peripherals 1330 (for example,peripherals 1330-A through 1330-N as described above with reference toFIGS. 26-29). Specifically, for implementations in which a machine 120includes a plurality of peripherals 1330, the device 1300 (i) polls eachof the plurality of peripherals 1330, (ii) processes a signal receivedfrom a particular peripheral 1330 of the plurality of peripherals 1330as described in methods 3100-3400, and (iii) responds to the particularperipheral 1330 from which the signal was received as described inmethods 3100-3400. For example, a machine 120 may include a billacceptor as a first peripheral 1330 and a coin acceptor as a secondperipheral 1330. In such a scenario, a mobile device 150 would beprovided with data related to signals received from the bill acceptoraccording to the concepts described in methods 3100-3400, and signalsreceived from the coin acceptor according to the concepts described inmethods 3100-3400.

Further, while the methods 3100-3400 refer to the peripheral 1330 as abill acceptor, the concepts described herein also apply to other typesof peripherals 1330. As described above, example peripherals 1330include bill acceptors, coin acceptors, and cashless payment devicessuch as payment card readers. Example peripherals 1330 may also includeany other type of electronic peripheral device related to or unrelatedto accepting payments.

Lastly, the operations of methods 3100-3400 are depicted in a particularorder, and at particular vertical offsets (spacing) with respect to eachother. Regarding the particular order, unless the description for aparticular operation states otherwise, the operations may be implementedout of the order depicted in the figures, especially with respect tooperations in different columns, and especially with respect tooperations described as being asynchronous. For example, theacknowledgement in operation 3104 is described (in more detail below) asbeing sent in response to the poll signal sent in operation 3102; assuch, this pair of operations and those similarly described must beimplemented in the order depicted in the figures. However, the pollsignal in operation 3106 may be sent before, at the same time as, orafter the poll signal sent in operation 3102, since the description ofthese operations does not state a particular order or include anytemporal limitations. Regarding the particular vertical offsets withrespect to the operations, these offsets are provided for purposes ofclarity and are not to temporal scale. As such, relative spacing sizesbetween operations have no effect on relative amounts of time that mustpass between execution of such operations.

As described above with reference to FIG. 30A, normal operations may becharacterized by the device 1300 relaying signals between the peripheral1330 and the machine controller 1360. FIG. 31 depicts example normaloperations in accordance with some implementations. Referring to FIG.31, the machine controller 1360 polls (3102) the device 1300, whichresponds (3104) with an acknowledgement. Asynchronously (compared tooperations 3102 and 3104), the device 1300 polls (1306) the peripheral1330, which responds (3108) with an acknowledgement. If the device 1300is not registered as a slave to the machine controller 1360 when beingpolled in operation 3102, the machine controller 1360 registers thedevice 1300 with a setup signal as described above with reference toFIG. 27 (operations 1404-1408). Similarly, if the peripheral 1330 is notregistered as a slave to the device 1300 when being polled in operation3106, the device 1300 registers the peripheral 1330 with a setup signalas described above with reference to FIG. 27 (operations 1414-1418).

The machine controller 1360 continues to poll the device 1300 at afrequency determined by the particular implementation of the MDBprotocol, and the device 1300 proceeds to poll the peripheral 1330 at afrequency determined either by the particular implementation of the MDBprotocol, or at any other predetermined frequency. Eventually, a paymentevent (3114) occurs at the peripheral 1330 (e.g., a $1 bill isreceived). Until the device 1300 receives a signal indicating thepayment event from the peripheral 1330, the device 1300 responds topolls from the machine controller 1360 with acknowledgements. As such,when the machine controller 1360 polls (3110) the device 1300 again, thedevice 1300 responds (3112) with an acknowledgement. Subsequent to thepayment event, the device 1300 polls (3116) the peripheral 1330, and theperipheral 1330 responds (3118) with a payment received signal,indicating the payment event 3114. For example, the payment receivedsignal is addressed to the machine controller 1360 and includes amessage indicating a $1 bill was received at the peripheral 1330 (asdepicted in FIG. 30A).

In response to receiving the payment received signal from the peripheral1330, the device 1300 (i) responds (3120) to the peripheral 1330 with anacknowledgement, and after receiving (3122) the next poll from themachine controller 1360, (ii) sends (3124) a payment received signal tothe machine controller 1360 (e.g., including the $1 received message).As described above with reference to FIGS. 28A-28B, the device 1300 mayrespond to the peripheral 1330 with the acknowledgement in operation3120 without waiting for any other operations or events to take place,but the device 1300 must wait for the next poll to be received (depictedin operation 3122) before having an opportunity to send the paymentreceived signal to the machine controller 1360 in operation 3124.

As described above with reference to FIG. 30B, intercept operations maybe characterized by the device 1300 relaying signals between theperipheral 1330 and an external device (e.g., a mobile device 150) viathe internal peripheral 1340 (rather than between the device 1300 andthe machine controller 1360). FIG. 32 depicts a transition from normaloperations to intercept operations in accordance with someimplementations. Referring to FIG. 32, an application executing on themobile device 150 may require access to an electronic peripheral device(e.g., peripheral 1330) in order to perform a function requested by auser. For example, the application receives (3202) a user request toprocess a cash transaction (e.g., in order to pay for a product orservice, in order to deposit money into an account, or for any of theother reasons described above). In response to the user request, themobile device 150 establishes (3204) a connection with the device 1300(e.g., via the internal peripheral 1340 as described above). In someimplementations, as part of the connection process, the mobile device150 sends to the device 1300 a request to access functionalityassociated with the peripheral 1330. In some implementations, as part ofthe connection process, the device 1300 validates the request, whereinvalidation of the request indicates that the mobile device 150 isauthorized, by a remote server (e.g., server 130) via a communicationcapability of the mobile device (e.g., a long-range communicationcapability), to access the signals generated by the peripheral 1330.Features of the implementations of the device validation process and theconnection process (between a mobile device 150 and the device 1300) aredescribed in more detail above with reference to FIGS. 7, 8A-8G, 9A-9E,and 23 (e.g., including the security unit 755 and the communicationsunit 770 shown in FIG. 20).

In response to connecting to the mobile device 150 and/or to the requestto access functionality associated with the peripheral 1330, the device1300 sends a reset signal (3206) and/or a setup signal (3208) to theperipheral 1330 in order to reconfigure the peripheral 1330 tocommunicate with the device 1300 (rather than with the machinecontroller 1360). As described above, the device 1300 reconfigures theperipheral 1330 to communicate with the device 1300 by resetting themaster address (the signal destination address) of the peripheral 1330to be the address of the device 1300. Upon resetting the master addressof the peripheral 1330 to the address of the device 1300, the device1300 effectively becomes the master to the peripheral 1330. As a result,the machine controller 1360 is no longer the master to the peripheral1330 (see FIG. 30B). By becoming the master to the peripheral 1330, thedevice 1300 appears to be the machine 120. In other words, theperipheral 1330 communicates with the device 1300 as if the device 1300were the machine 120 or the machine controller 1360 (e.g., theperipheral 1330 addresses signals to the device 1300 instead of to themachine controller 1360). For example, upon receiving $1 bill, a billcollector peripheral 1330 reports the receipt of the $1 bill to thedevice 1300 rather than to the machine controller 1360. As a result, themachine controller 1360 never receives any indications that a $1 billwas inserted into the bill collector of the machine 120, and thereforedoes not proceed with internal vending operations (does not allow aperson to purchase any products stocked in the machine or otherwiseapply a credit for purchasing any products, even though the personinserted money into the machine). Stated another way, any signalsreporting the receipt of the $1 bill at the bill collector areintercepted by the device 1300 and are not relayed to the machinecontroller 1360. Following the reset and/or setup signals, the device1300 receives (3210) an acknowledgement from the peripheral 1330.

Once the signal destination address of the peripheral 1330 is updated tobe that of the device 1300, the device 1300 continues to poll theperipheral 1330 (3212, 3216) and receive acknowledgements from theperipheral 1330 (3214, 3218). Polls received at the device 1300 from themachine controller 1360 (3222, 3226) during this time are not relayed tothe peripheral 1330. Instead, the device 1300 merely acknowledges (3224,3228) the polls so that the machine controller 1360 does not remove thedevice 1300 from its list of registered devices. Stated another way, thedevice 1300 normally passes signals received from the machine controller1360 to the peripheral 1330, but while performing intercept operations(as a result of the mobile device 150 connecting to the device 1300 andthe device 1300 resetting the peripheral 1330), the device 1300 stillresponds to polls received from the machine controller 1360, but doesnot pass any messages through to the peripheral 1330. Instead, thedevice 1300 just acknowledges messages received from the machinecontroller 1360. Accordingly, the device 1300 remains registered withthe machine controller 1360 and appears to be in an idle state (from thepoint of view of the machine controller 1360). While performingintercept operations, communications between (i) the device 1300 and themachine controller 1360 and (ii) the device 1300 and the peripheral 1330continue to be asynchronous. The device 1300 continues to performintercept operations until transitioning back to normal operations(described in more detail below with reference to FIG. 34).

FIG. 33 depicts intercept operations in accordance with someimplementations. Referring to FIG. 33, a payment event (3302) occurs atthe peripheral 1330 (e.g., a $1 bill is inserted into a bill acceptorperipheral 1330). In response to the next poll (3304) received from thedevice 1300, the peripheral 1330 sends a payment received signal (3306)to the device 1300 with a message indicating or otherwise associatedwith the payment event (e.g., $1 received). The device 1300 acknowledges(3308) the payment received signal and creates (3310) a transactionbased on the payment received signal. The transaction may include thesame message as that included in the payment received signal (e.g., $1received) and/or any related message optionally including additionalinformation (e.g., $1 received and not refunded).

The device 1300 transmits (3312) the transaction (more specifically, asignal including a message describing or otherwise associated with thetransaction) to the mobile device 150. The mobile device 150 forwards(3314) the transaction to the server 130 for further processing. Theserver 130 processes (3316) the transaction. For example, the server 130adds an amount of funds to the user's account in accordance with theamount of cash that was deposited as part of the payment event 3302(e.g., adds $1 to the user's account). As another example, the server130 sends an amount of funds to a recipient in accordance with theamount of cash that was deposited as part of the payment event 3302(e.g., sends $1 to the recipient). As another example, the server 130associates a specified product or service with the user's account inaccordance with a requested purchase (e.g., associates a virtual lotteryticket with the user's account in return for an amount of fundsassociated with the amount of cash that was deposited as part of thepayment event 3302).

As a result of the processing of the transaction, the server 130 sends(3318) a notification to the mobile device 150 indicating the paymentwas processed and/or a result of the payment being processed (e.g., apurchase confirmation or a deposit confirmation). In someimplementations, the mobile device 150 (more specifically, anapplication executing on the mobile device) displays information relatedto the received notification (e.g., an alert indicating a successfulpurchase or deposit, or an updated user interface indicating a newaccount balance).

Returning to the bill collector example, in some implementations,operations 3302 through 3312 are repeated each time a person inserts abill into the peripheral 1330. Optionally, the mobile device 150 groupssuccessive transactions (e.g., successive $1 insertions) into a singletransaction message and sends the transaction message in operation 3314for processing at the server 130. Alternatively, the mobile device 150sends transaction messages in operation 3314 for processing at theserver 130 for each successive transaction (e.g., successive $1insertions). In such implementations, operations 3302 through 3316 (oroperations 3302 through 3318, or operations 3302 through 3320) arerepeated each time a person inserts a bill into the peripheral 1330.

As the device 1300 performs the intercept operations described abovewith reference to FIG. 33, the device 1300 responds to polls (3322,3326) received from the machine controller 1360 with acknowledgements(3324, 3328) in order to remain registered with the machine controller1360 as described above with reference to FIG. 32.

FIG. 34 depicts a transition from intercept operations back to normaloperations in accordance with some implementations. Referring to FIG.34, the mobile device 150 receives or otherwise obtains (3402) anindication (e.g., via user input on the application executing on themobile device 150) that the mobile device 150 no longer requires accessto the peripheral 1330 (or functionality provided by the peripheral1330). For example, the user selects an affordance on a user interfaceof the application indicating that the transaction or deposit iscomplete (e.g., the user selects a “no” option when asked if the userwould like to purchase any more lottery tickets, or when asked if theuser would like to make any more deposits). In response to the accesscomplete notification 3402, the mobile device sends (3404) an accesscomplete notification to the device 1300 indicating that the mobiledevice 150 no longer requires access to the peripheral 1330 (orfunctionality provided by the peripheral 1330).

In response to receiving the access complete notification, the device1300 sends (3406) a reset signal to the peripheral 1330, thereby causingthe peripheral to no longer address signals to the device 1300. Thedevice 1300 proceeds to reset the signal destination address of theperipheral 1330 to be that of the machine controller 1360, for example,by sending (3416) a setup signal. As a result, subsequent messages sentby the peripheral 1330 to the device 1300 are addressed to the machinecontroller 1360. Stated another way, the machine controller 1360 onceagain functions as the master and the device 1300 once again functionsas a router of messages between the machine controller 1360 (master) andthe peripheral 1330 (slave).

As a result of the signal destination address of the peripheral 1330being reset to that of the machine controller 1360, the device 1300proceeds with normal operations as described above with reference toFIGS. 30A, 31, and 32. For example, the device 1300 acknowledges (3414)polls (3412) received from the machine controller 1360, andasynchronously polls (3416) the peripheral 1330. The device 1300receives acknowledgements (3418) from the peripheral 1330 and relaysmessages received from the peripheral 1330 to the machine controller1360.

FIGS. 35A-35B show a mobile device 150 with a graphical representationof a mobile application shown thereon, the mobile application being usedas part of a peripheral access system in accordance with someimplementations.

FIG. 35A depicts an example scenario in which the mobile device 150accesses a peripheral 1330 of a machine 120 in order to accept a cashpayment for the purchase of a virtual product (e.g., a lottery ticket)unrelated to any products stocked in the machine 120. In this example,the user's account has a balance of $3, and a user interface 3502 of themobile application prompts the user to insert $2 into the machine 120(e.g., after having connected to the machine 120 as a result ofoperation 3204, FIG. 32) in order to make a $5 purchase. When the userinserts $2 into the machine 120 and the transaction is processed asdescribed above with reference to operations 3302-3320 (FIG. 33), a userinterface 3504 of the mobile application notifies the user that the $5purchase was successful, and the new balance is $0. The notificationcorresponds with the acknowledgement in operation 3320 (FIG. 33).

FIG. 35B depicts an example scenario in which the mobile device 150accesses a peripheral 1330 of a machine 120 in order to accept a cashpayment for a deposit into the user's account. In this example, theuser's account has a balance of $3, and a user interface 3512 of themobile application prompts the user to insert $2 into the machine 120(e.g., after having connected to the machine 120 as a result ofoperation 3204, FIG. 32) as a result of the user selecting an option todeposit $2. When the user inserts $2 into the machine 120 and thetransaction is processed as described above with reference to operations3302-3320 (FIG. 33), a user interface 3514 of the mobile applicationnotifies the user that the $2 was successfully deposited, and the newbalance is $5. The notification corresponds with the acknowledgement inoperation 3320 (FIG. 33).

The implementations described with reference to FIGS. 30A-35B usespecific examples for illustration (e.g., the peripheral 1330 being abill acceptor, and the peripheral 1330 being accessed in order tosupport cash purchases or deposits). Other scenarios may be implementedby providing a mobile application access to an electronic peripheraldevice of a machine, the machine being otherwise unrelated to a deviceexecuting the mobile application. For example, a mobile application mayaccess a cash return peripheral of a machine 120 (e.g., a module forprocessing refunds at a vending machine 120 using, for example, aquarter return slot to provide quarter(s) or the bill acceptor to output$1 bill(s)) in order to support a function of the mobile applicationthat makes cash available to a user (e.g., receiving a peer-to-peer cashpayment, withdrawing cash from an account, receiving a cash refund for aproduct or service provided by the mobile application, receiving a cashreward as a result of an accomplishment in a gaming application,receiving a cash payment as a result of a winning virtual lotteryticket, and so forth).

Further, implementations need not be limited to scenarios involving cashtransactions. Other types of electronic peripheral devices may beaccessed from a machine 120 in order to extend functionality of a mobileapplication that would not otherwise have direct access to the hardwarenecessary to support such functionality. Stated another way, the device1300 enables a mobile device 150 to access functionality provided by anelectronic peripheral device 1300 of a machine 120 by providing wirelesscommunications between an application executing on the mobile device 150and the electronic peripheral device 1330, by (i) communicativelydecoupling the electronic peripheral device 1300 from the machinecontroller 1360 which normally would function as the master of theelectronic peripheral device 1330, and (ii) communicatively coupling theelectronic peripheral device 1300 with the mobile application whichfunctions as the master of the electronic peripheral device until themobile application no longer requires access to the functionalityprovided by the electronic peripheral device 1330.

MISCELLANEOUS

The foregoing description has been described with reference to specificimplementations. However, the illustrative discussions above are notintended to be exhaustive or to limit the claims to the precise formsdisclosed. Many variations are possible in view of the above teachings.The implementations were chosen and described in order to best explainprinciples of operation and practical applications, to thereby enableothers skilled in the art.

The various drawings illustrate a number of elements in a particularorder. However, elements that are not order dependent may be reorderedand other elements may be combined or separated. While some reorderingor other groupings are specifically mentioned, others will be obvious tothose of ordinary skill in the art, so the ordering and groupingspresented herein are not an exhaustive list of alternatives.

As used herein: the singular forms “a”, “an,” and “the” include theplural forms as well, unless the context clearly indicates otherwise;the term “and/or” encompasses all possible combinations of one or moreof the associated listed items; the terms “first,” “second,” etc. areonly used to distinguish one element from another and do not limit theelements themselves; the term “if” may be construed to mean “when,”“upon,” “in response to,” or “in accordance with,” depending on thecontext; and the terms “include,” “including,” “comprise,” and“comprising” specify particular features or operations but do notpreclude additional features or operations. Lastly, as used herein, theterms “master” and “host” are synonymous unless clearly statedotherwise.

What is claimed is:
 1. An electronic device for retrofitting a machineto provide external access to one or more electronic peripheral devicesof the machine, the electronic device comprising: a slave interfaceconfigured to couple the electronic device to a machine controller ofthe machine via a multi-drop bus (MDB); a host interface configured tocouple the electronic device to a first peripheral device of the one ormore electronic peripheral devices of the machine, wherein the firstperipheral device is configured to communicate via MDB protocol and isdecoupled from the MDB of the machine; a wireless transceiver; one ormore processors; and non-transitory memory storing one or more programsto be executed by the one or more processors, the one or more programscomprising instructions for: registering the electronic device as aslave to the machine controller; registering the first peripheral deviceas a slave to the electronic device; receiving, from a mobile device viathe wireless transceiver, a request to access signals generated by thefirst peripheral device; validating the request, wherein validation ofthe request indicates that the mobile device is authorized, by a remoteserver, to access the signals generated by the first peripheral device;and sending a first reset command to the first peripheral device via thehost interface, wherein the first reset command includes a directive toupdate a signal destination address of the first peripheral device froma controller address of the machine controller to a device address ofthe electronic device.
 2. The electronic device of claim 1, wherein theone or more programs further comprise instructions for: receiving, atthe host interface of the electronic device, a first signal from thefirst peripheral device, wherein the first signal is directed to theelectronic device in accordance with the updated signal destinationaddress; in response to receiving the first signal from the firstperipheral device: sending an acknowledgement to the first peripheraldevice via the host interface; transmitting a second signal to themobile device via the wireless transceiver for forwarding to the servervia a long-range communication capability of the mobile device, whereinthe second signal includes data associated with the first signalreceived from the first peripheral device; and forgoing provision of thefirst signal to the machine controller.
 3. The electronic device ofclaim 1, wherein the one or more programs further comprise instructionsfor: receiving, from the mobile device via the wireless transceiver, anotification to cease interaction with the mobile device; in response toreceiving the notification to cease interaction with the mobile device:sending a second reset command to the first peripheral device via thehost interface, wherein the second reset command includes a directive toupdate the signal destination address of the first peripheral devicefrom the device address of the electronic device to the controlleraddress of the machine controller.
 4. The electronic device of claim 1,wherein the one or more programs further comprise instructions for:receiving, at the slave interface of the electronic device, a firstcommand from the machine controller, wherein the first command isdirected to the first peripheral device; and in response to receivingthe first command from the machine controller: sending anacknowledgement to the machine controller via the slave interface in amanner as if originated from the first peripheral device; and relayingthe first command to the first peripheral device via the host interface.5. The electronic device of claim 1, wherein the one or more programsfurther comprise instructions for: receiving, at the host interface ofthe electronic device, a third signal from the first peripheral device,wherein the third signal is directed to the machine controller; and inresponse to receiving the third signal from the first peripheral device:sending an acknowledgement to the first peripheral device via the hostinterface in a manner as if originated from the machine controller; andrelaying the third signal to the machine controller via the slaveinterface.
 6. The electronic device of claim 1, wherein the instructionsfor registering the electronic device as a slave to the machinecontroller comprise instructions for: identifying the electronic deviceto the machine controller as the first peripheral device; and acceptingregistration of the electronic device as the first peripheral device. 7.The electronic device of claim 1, wherein the first peripheral device isa coin acceptor, a bill acceptor, or a payment card reader, and thefirst signal is a payment received signal.
 8. The electronic device ofclaim 1, wherein the machine is a vending machine, a parking meter, atoll booth, a laundromat washer or dryer, an arcade game, a kiosk, aphoto booth, a toll booth, or a transit ticket dispensing machine.
 9. Amethod of retrofitting a machine to provide external access to one ormore electronic peripheral devices of the machine, the methodcomprising: at an electronic device including a wireless transceiver,one or more processors, non-transitory memory, a slave interfaceconfigured to couple the electronic device to a machine controller ofthe machine, and a host interface configured to couple the electronicdevice to a first peripheral device of the one or more electronicperipheral devices of the machine, wherein the first peripheral deviceis configured to communicate via MDB protocol and is decoupled from theMDB of the machine: registering the electronic device as a slave to themachine controller; registering the first peripheral device as a slaveto the electronic device; receiving, from a mobile device via thewireless transceiver, a request to access signals generated by the firstperipheral device; validating the request, wherein validation of therequest indicates that the mobile device is authorized, by a remoteserver, to access the signals generated by the first peripheral device;and sending a first reset command to the first peripheral device via thehost interface, wherein the first reset command includes a directive toupdate a signal destination address of the first peripheral device froma controller address of the machine controller to a device address ofthe electronic device.
 10. The method of claim 9, further comprising:receiving, at the host interface of the electronic device, a firstsignal from the first peripheral device, wherein the first signal isdirected to the electronic device in accordance with the updated signaldestination address; in response to receiving the first signal from thefirst peripheral device: sending an acknowledgement to the firstperipheral device via the host interface; transmitting a second signalto the mobile device via the wireless transceiver for forwarding to theserver via a long-range communication capability of the mobile device,wherein the second signal includes data associated with the first signalreceived from the first peripheral device; and forgoing provision of thefirst signal to the machine controller.
 11. The method of claim 9,further comprising: receiving, from the mobile device via the wirelesstransceiver, a notification to cease interaction with the mobile device;in response to receiving the notification to cease interaction with themobile device: sending a second reset command to the first peripheraldevice via the host interface, wherein the second reset command includesa directive to update the signal destination address of the firstperipheral device from the device address of the electronic device tothe controller address of the machine controller.
 12. The method ofclaim 9, further comprising: receiving, at the slave interface of theelectronic device, a first command from the machine controller, whereinthe first command is directed to the first peripheral device; and inresponse to receiving the first command from the machine controller:sending an acknowledgement to the machine controller via the slaveinterface in a manner as if originated from the first peripheral device;and relaying the first command to the first peripheral device via thehost interface.
 13. The method of claim 9, further comprising:receiving, at the host interface of the electronic device, a thirdsignal from the first peripheral device, wherein the third signal isdirected to the machine controller; and in response to receiving thethird signal from the first peripheral device: sending anacknowledgement to the first peripheral device via the host interface ina manner as if originated from the machine controller; and relaying thethird signal to the machine controller via the slave interface.
 14. Themethod of claim 9, wherein registering the electronic device as a slaveto the machine controller includes: identifying the electronic device tothe machine controller as the first peripheral device; and acceptingregistration of the electronic device as the first peripheral device.15. The method of claim 9, wherein the first peripheral device is a coinacceptor, a bill acceptor, or a payment card reader, and the firstsignal is a payment received signal.
 16. The method of claim 9, whereinthe machine is a vending machine, a parking meter, a toll booth, alaundromat washer or dryer, an arcade game, a kiosk, a photo booth, atoll booth, or a transit ticket dispensing machine.
 17. A non-transitorycomputer readable storage medium storing one or more programs, the oneor more programs comprising instructions, which, when executed by anelectronic device including a wireless transceiver, one or moreprocessors, non-transitory memory, a slave interface configured tocouple the electronic device to a machine controller of the machine, anda host interface configured to couple the electronic device to a firstperipheral device of the one or more electronic peripheral devices ofthe machine, wherein the first peripheral device is configured tocommunicate via MDB protocol and is decoupled from the MDB of themachine, cause the electronic device to perform operations including:registering the electronic device as a slave to the machine controller;registering the first peripheral device as a slave to the electronicdevice; receiving, from a mobile device via the wireless transceiver, arequest to access signals generated by the first peripheral device;validating the request, wherein validation of the request indicates thatthe mobile device is authorized, by a remote server, to access thesignals generated by the first peripheral device; and sending a firstreset command to the first peripheral device via the host interface,wherein the first reset command includes a directive to update a signaldestination address of the first peripheral device from a controlleraddress of the machine controller to a device address of the electronicdevice.
 18. The non-transitory computer readable storage medium of claim17, wherein the instructions further cause the electronic device toperform operations including: receiving, at the host interface of theelectronic device, a first signal from the first peripheral device,wherein the first signal is directed to the electronic device inaccordance with the updated signal destination address; in response toreceiving the first signal from the first peripheral device: sending anacknowledgement to the first peripheral device via the host interface;transmitting a second signal to the mobile device via the wirelesstransceiver for forwarding to the server via a long-range communicationcapability of the mobile device, wherein the second signal includes dataassociated with the first signal received from the first peripheraldevice; and forgoing provision of the first signal to the machinecontroller.
 19. The non-transitory computer readable storage medium ofclaim 17, wherein the instructions further cause the electronic deviceto perform operations including: receiving, from the mobile device viathe wireless transceiver, a notification to cease interaction with themobile device; in response to receiving the notification to ceaseinteraction with the mobile device: sending a second reset command tothe first peripheral device via the host interface, wherein the secondreset command includes a directive to update the signal destinationaddress of the first peripheral device from the device address of theelectronic device to the controller address of the machine controller.20. The non-transitory computer readable storage medium of claim 17,wherein the instructions causing the electronic device to performoperations including registering the electronic device as a slave to themachine controller comprise instructions causing the electronic deviceto perform operations including: identifying the electronic device tothe machine controller as the first peripheral device; and acceptingregistration of the electronic device as the first peripheral device.